📘
Amnet is a programmatic advertising platform under the Dentsu network that provides data-driven solutions for digital media buying. It specializes in real-time bidding (RTB), audience targeting, and campaign optimization to enhance ad performance across digital channels. Amnet integrates advanced technologies to ensure precise audience segmentation and efficient ad delivery while maintaining transparency in media spend. Its capabilities align with Dentsu's mission of enabling seamless and measurable connections between brands and their target audiences.
Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Full-Funnel Events
- Collects and syncs the Amnet UID, enabling user identification and audience segmentation for targeted advertising.
- Enriches events with identifiers and contextual data to support attribution for RTB strategies.
- Sends structured, enriched server-side event payloads to support analytics and reporting on campaign performance.
- The Amnet UID is collected via the sync and sent with every event.
- The customer ID must be provided by Amnet and is sent on every event as
cid.
- 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.
- The integration works with first-party data, which may limit its utility if third-party or external audience data needs to be incorporated.
- Sync Available: Yes
- Required for Starter Kit: Yes
- Prerequisites: Amnet customer ID
- Documentation: See Additional Amnet Sync Documentation
- Captures the Amnet
uid value used for user identification and matching.
- Sent with every event to support audience targeting and attribution.
- Without this sync, events may not be accurately reflected in reporting.
- To collect the sync values (e.g.,
uid), you must implement an Amnet ID sync. Refer to the following documentation to complete the setup: Amnet - ID Sync Guide.
- Obtain your account's customer ID from your Amnet customer support team.
- From the integration library, add an Amnet integration. Then, fill out the Connection Parameters:
| Connection Parameter | Description |
|---|
CUSTOMER_ID | A unique identifier assigned to each customer, used to track and associate user data across sessions, devices, and platforms for analytics and targeting. |
- MetaRouter provides all of the event mappings that Amnet integrations typically require. You may add custom events, parameters, or mappings in accordance with Amnet's API documentation.
- In the Pipelines tab, add your Amnet 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: Customer ID. | $$CUSTOMER_ID$$ |
uid | Integer: Amnet UID. | integrations.amnet.uid |
sid | String: Anonymous ID. | anonymousId |
url | String: Page referrer URL. | context.page.referrer |
| Output Key | Description | Expected Input |
|---|
vars | String: Empty parameter for page event. | Enrichment – '' |
| Output Key | Description | Expected Input |
|---|
vars | Object: Cart and product details. | Expression – constructs object with event, cart ID, and product details |
| Output Key | Description | Expected Input |
|---|
vars | Object: Purchase and product information. | Expression – constructs object with event, order ID, cart value, and products |
These identifiers are mapped to Amnet to improve user matching. Without these IDs, any events sent to Amnet may not be accurately reflected in reporting. For your convenience, IDs are mapped as Global parameters to ensure they are added to every event.
| Attribute | Example | Sync Injector Required? |
|---|
uid | 5c299f0f-c409-4abc-bd10-4e17b5d12eb3 | Yes |
sid | 130161d0-8fee-4167-aa4d-d151eed27c6b | No |
- Coordinate with your Amnet representative to confirm that events are being received and processed correctly on their backend.
