Adobe provides organizations with actionable, real-time intelligence regarding their digital strategies and marketing initiatives. Data connectors let you import tracking data from third-party applications into Analytics, so you can gather and use data from one central location. If you use one of the partner products, you can create an integration that imports the application data into marketing reports. Once integrated, you can generate reports that include data from your application.
For example, an e-mail integration might want to use an e-mail partner to distribute an e-mail campaign. When visitors come to your Web site you want to know which ones came in response to your e-mail campaign. Data connectors integrate data from your e-mail partner into marketing reports so that you can determine this information to gauge the effectiveness of your e-mail campaign.
We will end-of-life the Adobe Data Connector technology on August 1, 2021. Learn more…
Data connectors should integrate appropriately with most popular browsers. However, reports look and function best on systems that meet the following recommendations:
Before configuring a data connectors integration for your product, do the following:
You must have a current account to access the Data Connectors landing page (console). It is also recommended that you are familiar with Adobe Analytics.
Log into the Adobe Experience Cloud.
Click Analytics > Admin > All admin > Data connectors.
Click Add New.
Step through the Add Integration interface.
Depending on the individual product integration, you might need to provide specific configuration information as part of the integration process.
When the integration completes, the partner product icon displays on the Data Connectors Network page and is available in menus.
After you activate an integration, it displays on the Data Connectors page. You can view details and make configuration changes on the console. You can view active integrations and integrations across all report suites in your company. You can also view an activity log, set an integration as a dashboard, configure an integration, and find help.
Remarketing segments are data files that are created based on the variables used in a data connectors integration.
Adobe Analytics sends these in separate daily files via data warehouse to an FTP created by Adobe for the third party. The third party then distributes these files to the client. Companies commonly use these to remarket to those that may have visited the site and looked at a product, but did not buy. (For example, you reach out to a client offering a discount to a product they viewed but did not end up purchasing it).
In order to successfully implement remarketing segments, the following conditions must be met:
If the product is defined without an associated event, the
prodView event automatically fires.
If the above requirements are not met, the corresponding remarketing segments are not reported correctly.
Cart Abandonment: fires after the user adds a product to the shopping cart:
Purchases: fires on the purchase confirmation page:
s.products="; cat;1;50"; s.events="purchase"; //Note: Though optional, adding the purchaseID variable increases accuracy by preventing duplicate purchases
|No product ID information is showing in Remarketing Segment file.||Occurs when the correct event fires, but no product variable is present on the same image request. In order to correct this, make sure the products variable and corresponding event fires on the same page, as seen in the implementation examples above.|
|Remarketing segment files are not received.||If you are not receiving your files, have one of your organization’s supported users contact ClientCare to investigate the cause of reports not successfully being received.|
It is common for consultants to also set up a data warehouse request as a daily scheduled report in addition to your standard data connectors integration remarketing segment file. This data warehouse request would include data connectors variables as well as non-data connectors variables, and the request can be scheduled based only on your organization’s specific request. To prevent confusion when troubleshooting, specify whether the file in question is the actual remarketing segment file, or a data warehouse request containing non-genesis variables.