- 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
- Configuring Trait Expiration with the Time to Live (TTL) Setting
- 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
Using best practices on SPA pages when sending data to AAM
In this document, we will describe several best practices that you should follow and be aware of as you are sending data from Single Page Applications (SPA) to Adobe Audience Manager (AAM). This doc focuses on using Experience Platform Launch, which is the recommended implementation method.
Initial Notes
- The items below are going to assume that you are using Platform Launch to implement on your site. The considerations would still exist if you are not using Platform Launch, but you would need to adapt them to your implementation method.
- All SPAs are different, so you may need to tweak some of the following items to best meet your need, but we wanted to share some best practices with you; things that you need to think about as you are sending data from SPA pages to Audience Manager.
Simple diagram of working with SPAs and AAM in Experience Platform Launch
As stated, this is a simplified diagram of how SPA pages are handled in an Adobe Audience Manager implementation (without Adobe Analytics) using Platform Launch. As you can see, it is fairly straight-forward, with the big decision being how you are going to communicate a view change (or an action) to Platform Launch.
Triggering Launch from the SPA page
Two of the more common methods for triggering a rule in Platform Launch (and therefore sending data into Audience Manager), are:
- Setting JavaScript custom events (see example HERE with Adobe Analytics)
- Using a Direct Call Rule
In this Audience Manager example, we are going to use a Direct Call rule in Launch to trigger the hit going into Audience Manager. As you’ll see in the next sections, this really becomes useful by setting the Data Layer to a new value, so that it can be picked up by the Data Element in Platform Launch.
Demo Page
We have created a small demo page that demonstrates changing a value in the data layer and sending it into AAM, as you may do on a SPA page. This functionality can be modeled for more elaborate changes needed. You can find this demo page HERE.
Setting the data layer
As mentioned, when new content is loaded on the page or when someone performs an action on the site, the data layer needs to be set dynamically in the head of the page BEFORE Launch is called and runs the rules, so that Platform Launch can pick up the new values from the data layer and push them into Audience Manager.
If you go to the demo site listed above and look at the page source, you will see:
- The data layer is in the head of the page, before the call to Platform Launch
- The JavaScript in the simulated SPA link changes the Data Layer, and THEN calls Platform Launch (the _satellite.track() call). If you were using JavaScript custom events instead of this Direct Call Rule, the lesson is the same. First change the data layer, and then call Launch.