Best Practices for the Adobe Ads Integration

Updated 

A SiteCatalyst Report Suite generally represents a web property or a grouping of web properties. For example, a Web Property is a website, but a grouping could be multiple Apps reporting into the same rolled-up Report Suite.

When configuring the integration in Sprinklr Marketplace, you must add and configure each of these metrics in order to report in Sprinklr.

The Web Analytics Profile Builder allows you to set up automated tracking code tagging on all Outbound Posts containing links back to their Web Properties. Although this is not technically required for the integration to work. Also, by using this feature you will have 100% compliance internally with tagging on all posts.

In order for this integration to work, there must be a unique identifier in the tracking code for Sprinklr to map web traffic back to the Outbound Post. If this is not already in place with your structure, then you will have to modify your setup to include a unique value (preferably Post ID) in one of the parameters.

Data is updated in every hour in Sprinklr

Yes, If you have unique identifier present in your Ads at any level. Sprinklr will best identify the level of uniqueness and map the data back to your Ad entity.

Sprinklr smartly compares and identifies at which level your identifier is unique.

If your Identifier is unique at Ad Level you will be able to understand the split of the Data across your Ads.

If your identifier is not unique at Ad Level Sprinklr identifies and attribute it Ad Set Level

If your identifier is not unique at Ad Set Level, Sprinklr identifies and attribute it to Paid Initiatve Level

If your idnetifier is not unique at any level then, Sprinklr will still store the data but it wont be attributed to any entity.

Adobe data can be backfilled for last 2 years from the current date.

All the Adobe Analytics reporting data will populate in the GMT timezone by default.