This Integration Guide explains how to enable the Fiksu data connector within the Adobe Marketing. Fiksu Integration Guide

Transcription

1 This Integration Guide explains how to enable the data connector within the Adobe Marketing Cloud. Integration Guide 1

2 Intended Audience This document is intended for professionals and online marketers who are familiar with configuring Adobe Analytics, including Adobe Analytics variables (evars, s, and props), and are familiar with the platform. INTEGRATION OVERVIEW This Adobe Marketing Cloud integration combines the power of s mobile marketing platform through mobile-first data, extensive reach into mobile ad channels and advanced optimizations with the behavioral tracking, targeting and reporting of the Adobe Marketing Cloud to create powerful analytics and optimization opportunities for your organization. I. Key Benefits and Features Key Benefits of the Adobe- integration include: Simple integration configuration and monitoring Consolidated mobile marketing and analytics data into one reporting interface Automated daily sync of mobile marketing measurement data within Adobe Analytics Optimization of mobile user acquisition and branding campaigns by combining mobile attribution and tracking with usage data Mobile Marketing and Analytics Data The -Adobe integration can be configured to (a) automatically import mobile campaign performance data, and (b) optionally, device level attribution so you can further maximize returns from your mobile marketing spends. Performance Reporting: Once integrated automatically uploads campaign performance metrics (impressions, clicks, spend and conversions or actions), broken down by date and source for campaigns. User acquisition and Re-engagement performance data are reported separately. Device Attribution: You can optionally enable device attribution to analyze the full value of -driven users against all the s tracked by Adobe. Both attributed and organic data is uploaded to Adobe Analytics. Uploaded data includes acquisition date and source (network) information on a per device level. *Note: Due to data policy contracts, no Facebook or Twitter attribution data will be passed to Adobe. These devices will show as Organic. What You Should Know Before Activating This Integration Before activating this integration, review the following items against your deployments of Adobe Analytics and your account. Doing so will ensure the appropriate best practices and prerequisites are in place prior to activation, resulting in an optimal and successful integration. Optional Step: Please be advised that you might need to modify your Adobe and SDK integrations in order to take advantage of device attribution data. 2

3 Adobe Analytics Review the following information about this integration as it relates to Adobe Analytics: Report-Suite Specific: Be advised this integration is report-suite specific. Ensure that you have selected the desired report suite prior to activating the integration. Prerequisites for Device Attribution: In order to receive Device Attribution data you must have the Marketing Cloud Visitor Service active in your app and Customer Attributes Service active in the Marketing Cloud. The integration requires that you sync the Customer Attributes Alias ID with the Adobe Marketing Cloud Visitor ID. The Alias ID for this integration is CustID. This unique ID should also be sent to using the ClientID capability in the SDK. -Adobe Integration Review the following information about this integration as it relates to : Current Customer of : This integration requires you to be a customer of. If you are not currently a customer, and do not have an active account, you will not have the information necessary to complete the integration wizard. If you are a customer, your Account Manager will be able to provide you with the following information necessary to complete the integration wizard: o Customer ID: In order to complete the integration setup you will need to have your Customer ID. Please contact your Account Manager if you have questions. o App Key: You will also need a App ID for each app you intend to integrate with your Adobe Analytics report suite. Please contact your Account Manager if you have questions. Adobe Pricing Considerations Please note, there may be implementation fees associated with this integration in accordance with your Adobe contract. Please contact your Adobe Account Representative for pricing details. Pricing Considerations This is integration is provided to customers at no additional cost. Please contact your Account Manager for further details. Adobe Analytics Integration s This integration uses Adobe Analytics variables to track various metrics. After identifying or creating the Success s, Classifications and evars to use with the integration, use Adobe Analytics Admin Console to enable them. The following table describes the Adobe Analytics variables needed for this integration. NOTE: Each integration will require an independent set of variables, classifications and success s to accurately import and merge data. An overlap of variables, s or classifications will result in an incorrect consolidation and aggregation of your campaign results. 3

4 II. Adobe Analytics s A. Required s Type Properties Population Method evar Type: String Expire After: Never Status: Allocation: Most Recent fiksu_ua_campaign_key Key created by unique to Ad network/ type combination for User Acquisition campaigns fiksu_ua_impressions Number of impressions served by campaigns fiksu_ua_clicks Number of clicks served by campaigns Type: Currency fiksu_ua_cost Spend on Campaigns fiksu_ua_conversions Number of conversions reported for a User Acquisition campaign B. Optional s Type Properties Population Method evar Type: String Expire After: Never Status: fiksu_reng_campaign_key Key created by unique to Ad network/ type combination for Reengagement Campaigns 4

5 Allocation: Most Recent fiksu_reng_impressions Number of impressions served by campaigns fiksu_reng_clicks Number of clicks served by campaigns Type: Currency fiksu_reng_cost Spend on Campaigns fiksu_reng_actions Number of post install actions resulting from re-engagement campaign III. Integration Procedure The Adobe Integration Wizard walks you through the integration process. (Optional) Prerequisite for Device Attribution data: 1. Download the Customer Attribute FTP template from the Data Connectors Showcase under Resources" 2. In the Adobe Marketing Cloud, create a Customer Attribute utilizing CustID as the Alias ID and the downloaded template as the FTP schema To configure the integration: 1. In the Adobe Marketing Cloud, select Data Connector from the product drop-down list. 2. Click Add New and select By in the Show drop down list. 3. Find the icon and drag it to an empty plug-in slot in your Adobe Analytics report suite to launch the Integration Wizard. 4. On the Integration introduction page, review the text, then review Adobe s Terms & Conditions associated with the integration. 5. Select the Report Suite that you want to use for this integration. 5

6 6. Provide a user-friendly name to identify this integration, then click Create and Configure this Integration. This page provides an overview of the integration, along with helpful links for more information. Contact your appropriate Account Managers at both organizations for further details. 7. On each page of the Integration Wizard, provide the information, as described in the following table: Field Integration App Key Customer ID Customer Attribute FTP Host Customer Attribute FTP Password Customer Attribute FTP User UA Campaign Key Configuration Section Integration name that Analytics displays in the report suite s Active Integration List of the person who is responsible for this integration address that receives all notifications related to this integration of the organization-specific purpose for the integration Unique key for each app registered with. Your contact will provide this key Unique Key for your account with. Your contact will provide this key Host address for Customer Attribute Password for the FTP Account created for Customer Attributes User for the FTP Account created for Customer Attributes Appropriate evar dedicated to User Acquisition performance reporting (Required) Reng Campaign Key Appropriate evar dedicated to Re-engagement performance reporting (Optional) UA Impressions Adobe Analytics that stores the impressions metric imported from (Required) UA Clicks Adobe Analytics that stores the clicks metric 6

7 (Required) UA Cost Adobe Analytics that stores the cost metric (Required) UA Conversions Adobe Analytics that stores the Conversion metric associated to User Acquisition Campaigns (Required) Reng Impressions Adobe Analytics that stores the impressions metric imported from (Optional) Reng Clicks Adobe Analytics that stores the clicks metric (Optional) Reng Cost Adobe Analytics that stores the cost metric (Optional) Reng Actions Adobe Analytics that stores the Actions metric associated to Reengagement Campaigns (Optional) Select Calculated Metrics **API Access Requests (3) Data Appropriate calculated metrics to make accessible in reporting (3) Data Allow to access your reports. will use this API call to synchronize and upload accurate performance data. Note: This step is extremely important to keep performance data up to date. After Integration Please give 24 hours for data to start automatically populating into Adobe Analytics. You should be able to view all of your campaign data in the default dashboard provided with this integration. IV. Verifying the Integration In addition to the verification that will be done by your implementation consultant, you can ensure that data is successfully arriving in Adobe Analytics by performing the following checks. Validate the imports: Verify if you have an active campaign running with In Adobe Analytics, navigate to the Dashboard related to your App Key. Depending on your configuration, one of below actions should indicate a successful integration: o View the UA performance report for the past 2 days to ensure that you see one of the selected o o metrics in the report. View the Re-engagement performance report for the past 2 days to ensure that you see one of the selected metrics in the report. View your reports associated with the DeviceID evar and associated classification for the past 2 days to ensure that you are seeing the selected metrics tied to a classification. 7