Server-Side Forwarding FAQ

Frequently asked questions about features, functionality, and issues related to server-side forwarding.

Contents:

Tracking Servers

Question Answer

What if I'm currently using the legacy, tracking server based server side forwarding?

The legacy tracking server based server side forwarding method will continue to forward data from Analytics to Audience Manager, however if you wish to send Audience Manager segments into Analytics, the new report suite based server side forwarding is required. Additionally, there is no harm in enabling a report suite for server side forwarding on top of your tracking server configuration - the new report suite server-side forwarding setting will be used whenever there is a conflict.

Should I migrate my legacy tracking server based server side forwarding to the new report suite based server side forwarding?

We will continue to support the tracking server based server side forwarding for the foreseeable future, however if you want to take advantage of the integration from Audience Manager to Analytics (segment sharing to Analytics), then you'll need to enable the new report suite based server side forwarding for all applicable report suites. There is no urgent reason to disable the legacy tracking server based server side forwarding however.

Tagging and Reporting

Question Answer

What if I have multi-suite tagging on my site? Will server-side forwarding double my server calls to Audience Manager?

No, a hit that is forwarded from Analytics to Audience Manager will only be forwarded once to Audience Manager regardless of the number of report suites in the hit. If you have corresponding data sources in Audience Manager for each of the report suites in the hit, each will be populated appropriately from that single hit.

Keep in mind however, that if you currently use client-side data collection (DIL) and you enable server-side forwarding without installing the Audience Management Module, you will double your server calls to Audience Manager regardless of the number of report suites you have in your Analytics hit.

What if I have multi-suite tagged report suites that are mapped to separate IMS Orgs?

You should never send data from a single Analytics hit to two report suites that belong to separate IMS Orgs, but if this does occur, we will only forward the hit to the IMS Org matching the Marketing Cloud ID Service setup on the page.

What if I have multi-suite tagging and only one of my report suites is mapped to my IMS Org and the other is not?

We will forward the hit to the corresponding data collection server for the IMS Org on your mapped report suite, however since the non-mapped report suite will not have an associated data source in Audience Manager, no data will be recorded for the un-mapped report suite in Audience Manager.

What if I have a report suite that is mapped to multiple IMS Orgs?

Analytics will consider this report suite as unmapped and will not allow server side forwarding to be enabled for this report suite. Contact customer care to resolve this mapping issue.

Will the report suite based server side forwarding method be slower than the tracking server based server side forwarding?

No, the response time will be the same.

What if we have two IMS Orgs (or AAM instances) and want to share data between both IMS Orgs? Can I server side forward a single Analytics hit to multiple IMS Orgs?

No. If you need to share data collected under one IMS Org to another IMS Org, we recommend sending any applicable audiences from one Audience Manager instance to another using the audience marketplace.