- Overview
- Intro to Audience Manager
- Setup and Admin
- Web Implementation
- Mobile Implementation
- Audience Marketplace
- Build and Manage Audiences
- Data Explorer
- Using the Signals Dashboard to Quickly View Top Available Signals
- Using Data Explorer to Search for Used and Unused Key/Value Pairs
- Saving Searches in Data Explorer for Convenience in Re-use
- Using Data Explorer to Create Retroactive Traits and Segments
- Using Data Explorer to Validate Trait Creation for Your Onboarded Data
- Using Data Explorer to Work with Signals Coming from Adobe Analytics
- Traits and Segments
- Planning Trait Creation from Analytics Data
- Creating a Trait Taxonomy
- Creating Rule-based Traits
- Creating Onboarded Traits
- Creating Conversion Traits
- Choosing a Data Source when Creating Traits
- Using Code View to Create and Edit Traits
- Introduction to Bulk Management (BAAAM)
- The Basics of Creating Segments
- Creating a Segment Taxonomy
- Practical Segment Definition and Creation
- Creating Segments from Multiple Data Sources
- Choosing a Data Source when Creating a Segment
- Enhancing your Segments with Trait Recommendations
- Trait Recommendation Enhancements in the Segment Builder
- Using Recency and Frequency in Segments
- Using Code View when Building Segments
- Building a Segment to Suppress Ads to Customers
- Mapping Audience Manager Segments to Destinations
- Mapping Segments to a Device-based Destination
- Understanding Numbers in the Trait Graph
- Understanding Numbers in the Segment Graph
- Customer Tips - Traits and Segments Best Practices
- Algorithmic Models
- Understanding Predictive Audiences
- Configure and Report on Predictive Audiences
- Creating a First Party Look-Alike Model
- Excluding Traits in Algorithmic (Look-Alike) Models
- Increase ROAS by Using Algorithmic (Look-Alike) Models
- Using Look-Alike Models to Extend Sold Out Inventory from Your 1st Party Data
- Profile Merge
- Profile Merge Rules
- Overview of Profile Merge Rules
- Profile Merge Rule Examples and Use Cases
- Choosing the Right Profile Merge Rule
- Creating and Using Simple Profile Merge Rules
- Using Profile Merge Rules to Personalize in an Authenticated State
- Using Profile Merge Rules for Device Extension and Increased Reach
- Overview of Profile Merge Rule Enhancements
- Profile Merge Rule Enhancements - Pre-Requisites
- How Profile Merge Rule Enhancements Impact Segmentation, Activation, and Reporting
- Interpret Audience Identity Reporting
- Understanding Cross-Device Metrics in Audience Manager
- Customer Tips - Getting the most out of Profile Merge Rules
- Data Explorer
- Data Activation
- Destinations Basics
- Audience Lab
- People-Based Destinations
- People-Based Destinations Videos and Tutorials
- People-Based Destinations Data Flow
- Creating a Data Source for People-Based Destinations
- Understanding Hashed PII Data Ingestion for People-Based Destinations
- Ingesting Hashed PII for People-Based Destinations
- Using setCustomerIDs() to Ingest and Hash PII as a Declared ID
- Configuring Profile Merge Rules for People-Based Destinations
- Creating Segments for People-Based Destinations
- Create and Configure People-based Destinations
- Understanding and Configuring the LinkedIn People-Based Destination
- Understanding and Configuring the Google Customer Match People-Based Destination
- Reports
- Other Integrations
- API
Migrating from Tracking Server to Report Suite-Level Server-Side Forwarding
This article and video will show you how to enable server-side forwarding of Analytics Data to Audience Manager at a report suite level instead of at a tracking server level.
Introduction
If you have Adobe Audience Manager AND Adobe Analytics, you can implement “Server-side Forwarding” of the Analytics data to Audience Manager. This means that, instead of your page sending 2 hits (one to Analytics and one to Audience Manager), it can simply send a hit to Analytics, and Analytics will forward that data to Audience Manager. If you already have this up and running, and if you had it enabled/implemented before October 2017, your server-side forwarding might be based on your “Tracking Server”, which had to be enabled by Adobe Customer Care or Adobe Consulting. As of October 2017, you can now configure server-side forwarding yourself, and do it at a Report Suite level (forwarding PER Report Suite). There are significant benefits to this, which will be discussed below.
Tracking Server Forwarding
Your tracking server is the location to which you are sending your Analytics data, and also the domain at which the image request and cookie is written. It should be set in DTM or Experience Platform Launch, or in the AppMeasurement.js file, and will typically look like this, with your site or business name replacing “mysite”:
s.trackingServer = "mysite.sc.omtrdc.net";
If server-side forwarding is set up to forward at the tracking server level, any hit that is being sent to this tracking server (IF the Experience Cloud ID Service is also enabled) will be forwarded to Audience Manager. This had to be enabled by Adobe Customer Care or Adobe Consulting. They are also the ones who can disable it, AFTER you have switched over to report suite forwarding, as described below.
If you are unsure if tracking server forwarding is enabled for you, contact Adobe Customer Care or Adobe Consulting, and they should be able to let you know.
Report Suite-Level Server-Side Forwarding
One of the biggest benefits to moving to report suite forwarding from tracking server forwarding is that you will now be able to use “Audience Analytics”, which is the ability to forward Audience Manager segments back into Adobe Analytics for detailed segment analysis. This great feature is NOT supported if you are still on tracking server forwarding and not report suite forwarding. See more information about Audience Analytics in the documentation.
Important Tip
As stated in the video above, once you have all of the report suites set to forward that you want to forward to Audience Manager, you should contact Adobe Customer Care or Adobe Consulting and have them disable the tracking server forwarding. It is not an emergency for you to do this, because having both tracking server forwarding and report suite forwarding will NOT result in duplicate hits. However, it is best practice to only have report suite forwarding on. If you leave tracking server forwarding on, not only might it forward data from report suites that you do not want forwarded, but in the future, after you (and everyone at your company) has forgotten that tracking server forwarding is on, you might think that data is not forwarding for a specific report suite (because it is not turned on at the report suite level), but the data is still being forwarded anyway because of the tracking server. Then you will waste time and money figuring out why it is forwarding and also paying for AAM server calls that you didn’t expect. So it’s just a good idea to disable tracking server forwarding as soon as you have all of the report suites set to forward that make sense for your business needs.