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 analytics across various channels, including digital, TV, and social media. Amobee's technology leverages data to deliver personalized advertising campaigns, aiming to enhance audience engagement and return on investment. By utilizing machine learning and data analytics, Amobee helps brands understand consumer behavior and optimize their marketing strategies.
Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Full-Funnel Events
- Sends server-side event data to Amobee via beacon requests.
- Eliminates the need for an Amobee tag on the site, reducing client-side load.
- Sends the Amobee
uid for consistent user identification across platforms and touchpoints.
- Supports page, product, cart, and order lifecycle events, with a catch-all beacon for uncategorized events.
- All parameters in the default playbook are required.
- A unique beacon ID must be provided for each tracked event type, plus a catch-all beacon ID for events not specifically covered.
- The Amobee
uid is required on every event and is mapped as a global parameter so it is added to all events.
- The Amobee client ID must be entered into the
cid enrichment.
- In our testing, requests above ~20,000 characters in the URL began to fail. While this isn't a formally documented limit, it may be a practical constraint to consider when using this integration.
- All values must be URL-encoded and arrays pipe-delimited.
- One request per event; batching not supported.
- Complex lists (e.g., products) must be pipe-delimited.
- Sync Available: Yes
- Required for Starter Kit: Yes
- Prerequisites: Amobee client ID
- Documentation: See Additional Amobee Documentation
- Captures the Amobee
uid value used to identify users across events.
- Required by Amobee for successful user matching.
- Without this sync, events sent to Amobee will be rejected.
- To collect the sync values (e.g.,
uid), you must implement an Amobee ID sync. Refer to the following documentation to complete the setup: Amobee - ID Sync Guide.
- Ask Amobee representatives for the following credentials:
- Client ID
- Beacon IDs for each tracked event
- 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. |
- 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.
- In the Pipelines tab, add your Amobee integration.
- Select the correct integration revision.
- Click Add Integration to finalize deployment.
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 – '' |
uid | String: User ID provided by Amobee for identifying the user across all events. | context.providers.amobee.uid |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for page views. | $$PAGE_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for products searched. | $$PRODUCTS_SEARCHED_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for product list viewed. | $$PRODUCT_LIST_VIEWED_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for product viewed. | $$PRODUCT_VIEWED_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for product added to cart. | $$PRODUCT_ADDED_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for cart viewed. | $$CART_VIEWED_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Beacon ID for order completed. | $$ORDER_COMPLETED_BEACON_ID$$ |
| Output Key | Description | Expected Input |
|---|
b2 | String: Catch-all beacon ID for events not specifically categorized. | $$CATCH_ALL_BEACON_ID$$ |
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.
| Attribute | Example | Sync Injector Required? |
|---|
uid Required | 8575821199332081695 | Yes |
- Coordinate with your Amobee representative to confirm that events are being received and processed correctly on their backend.
