Amobee is a global marketing technology company that provides data-driven solutions for advertisers and agencies. It offers an integrated platform for media planning, buying, and real-time analytics across various channels, including digital, TV, and social media. Amobee's technology leverages data to deliver personalized and effective advertising campaigns, aiming to enhance audience engagement and return on investment. By utilizing advanced machine learning and data analytics, Amobee helps brands understand consumer behavior and optimize their marketing strategies.
What are the benefits of integrating MetaRouter with Amobee?
Enhanced Data Accuracy and Privacy: By using a server-side connection, MetaRouter ensures that all events and parameters are accurately and securely delivered to Amobee, reducing data loss and enhancing user privacy compared to client-side tagging.
Improved Website Performance: Eliminating the need for an Amobee tag on the site reduces the client-side load, leading to faster page load times and a better user experience.
Streamlined Identity Management: MetaRouter's ability to send the Amobee uid for identity ensures seamless and consistent user identification across different platforms and touchpoints, improving the effectiveness of targeted advertising campaigns.
Once logged in, locate and click on your profile or account icon, usually found in the top-right corner of the interface.
Navigate to Integration or API Settings:
In the account settings menu, look for sections labeled "Integration," "API," or similar. This is where integration details, including the Client ID, are typically found.
Locate the Client ID:
Within the Integration or API settings, search for the Client ID. It may be listed alongside other API credentials or integration details.
Contact Support if Needed:
If you cannot find the Client ID, contact Amobee support or consult the Amobee Help Center for specific instructions tailored to your account setup.
Gather Beacon IDs - Please reach out to your Amobee support team to gather IDs from your Amobee beacons.
Getting Started - From Your MetaRouter Account
Adding an Amobee integration.
From the integration library, add an Amobee integration. Then, fill out the Connection Parameters:
Connection Parameter
Description
PAGE_BEACON_ID
Identifies page views.
PRODUCTS_SEARCHED_BEACON_ID
Tracks searches for products.
PRODUCT_LIST_VIEWED_BEACON_ID
Logs views of product lists.
PRODUCT_VIEWED_BEACON_ID
Captures individual product views.
PRODUCT_ADDED_BEACON_ID
Records when products are added to the cart.
CART_VIEWED_BEACON_ID
Monitors views of the shopping cart.
ORDER_COMPLETED_BEACON_ID
Tracks completed orders.
CATCH_ALL_BEACON_ID
Acts as a fallback for any other events not specifically covered by the above beacons.
Adding an Amobee Sync
To gather the Amobee uid value, you must add an Amobee sync.
From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
In the Identity Syncs section, select the Amobee sync.
Fill out the following fields:
Consent Type
Client ID - Your Amobee account’s unique client ID.
API Timeout (in milliseconds) - Sets a time limit for how long the Sync Injector will wait for an API response from the vendor. The maximum timeout value is 300ms.
300 default
Cookie Lifetime (in days) - 365 default
Fire on Re-Sync - ON default
Scroll down and click the Save and Build File button.
Deploy your AJS file to propagate changes to your web property.
Event Mappings
MetaRouter provides all of the event mappings that Amobee integrations typically require. You may add custom events, parameters or mappings in accordance with Amobee’s API documentation. Please note, all parameters in the default playbook are required.
Global
Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.
Output Key
Description
Expected Input
cid
String: Input your Amobee client ID.
Enrichment - staticString: ''
uid
String: User ID provided by Amobee for identifying the user across all events.
These identifiers must be mapped to Amobee in order for successful user matching to occur. Without these IDs, any events sent to Amobee will be rejected. For your convenience, required IDs are mapped as Global parameters to ensure they are added to every event.
