Documentation

Amperity

Suggest Edits

📘

This integration is currently in beta. Contact your MetaRouter support team to get started.

What Is Amperity?

Amperity is a customer data platform (CDP) designed to help businesses unify and analyze their customer data from various sources. It uses advanced machine learning algorithms to create a comprehensive and accurate single view of each customer, enabling personalized marketing and improved customer experiences. Amperity's platform offers data integration, identity resolution, and segmentation capabilities, making it easier for companies to manage and utilize their customer data effectively. It also provides robust analytics tools that help businesses gain insights into customer behavior, preferences, and trends, ultimately driving better decision-making and more targeted marketing strategies.

What are the benefits of integrating MetaRouter with Amperity?

  • Streamlined Data Delivery: Integrating MetaRouter with Amperity ensures all events and parameters are delivered via a server-side connection, eliminating the need for an Amperity tag on the site, thereby reducing client-side overhead and improving site performance.
  • Enhanced Data Accuracy: Server-side integration helps in capturing more accurate and complete data by minimizing the risks of data loss or discrepancies that can occur with client-side tagging.
  • Improved Data Management: The integration simplifies data management by centralizing data collection and routing through MetaRouter, making it easier to maintain and update data flows while ensuring consistent data quality for Amperity’s analytics and customer insights.

Getting Started - From Your Amperity Account

  • Create a write access token - Please see a reference on how to create your token here.
  • Obtain your tenant ID - Please see a reference on how to find your tenant ID here.
  • Obtain your stream ID - Please see a reference on how to find your stream ID here.

Getting Started - From Your MetaRouter Account

Adding an Amperity integration.

From the integration library, add an Amperity integration. Then, fill out the Connection Parameters:

Connection ParameterDescription
TENANTA unique identifier assigned to a specific organization or instance of the Amperity platform.
TOKENWrite access token.
STREAM_IDA stream ID in Amperity is a unique identifier assigned to a specific data stream used for real-time data ingestion and integration within the Amperity platform.

Event Mappings

MetaRouter provides all of the event mappings that Amperity integrations typically require. You may add custom events, parameters or mappings in accordance with Amperity’s API documentation.

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 KeyDescriptionExpected Input
messageId
Required		String: ID used to identify a single event.messageId
anonymousId
Required		String: Anonymous ID is used for tracking and attribution. It should be a persistent, unique identifier (like a UUID) for an unauthenticated user.anonymousId
userId
Required		String: User ID is used for tracking and attribution. It should be a persistent, unique identifier (like a hashed email or database ID) for an authenticated user.userId
originalTimestamp
Required		String (ISO 8601 format): The original timestamp of the event.originalTimestamp
timestamp
Required		String (ISO 8601 format): The timestamp when the event was recorded.timestamp
context.userAgent RequiredString: The user agent string of the device.context.userAgent
context.providersObject: Depending on your configuration, the providers object may contain identifiers gathered by the Sync Injector. These should be mapped in the appropriate integrations to power downstream functionality that is reliant upon third-party identifiers.context.providers
traits
Required		Object: Traits or attributes of the user. These are key-value pairs that describe the user, such as email, name, age, etc. Refer to https://docs.metarouter.io/docs/event-method-identify#traits. The AJS traits object is mapped in its entirety to properties.traits
event
Required		String: The type of event, transformed to replace spaces with underscores and converted to lowercase.N/A - Expression

Required & Recommended Identifiers

These identifiers must be mapped to Amperity in order for successful user matching to occur. Without these IDs, any events sent to Amperity will be rejected. For your convenience, required and recommended IDs are mapped as Global parameters to ensure they are added to every event.

AttributeExampleSync Injector Required?
messageId
Required		abc123def456ghi789No
anonymousId
Required		130161d0-8fee-4167-aa4d-d151eed27c6bNo
userId
Required		user-5678-wxyz-1234-abcdNo
userAgent
Required		Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36No
context.providers
Recommended		{
"google_analytics": {
"gclid": "1234567890.1234567890"
},
"clinch": {
"clinch-sid": "anon-1234-abcd-5678-efgh"
}
}		Yes*
traits
Required		{
"email": "[email protected] ",
"name": "John Doe",
"age": 30,
"premiumUser": true
}		No

*Depending on your configuration, the providers object may contain identifiers gathered by the Sync Injector. These should be mapped in the appropriate integrations to power downstream functionality that is reliant upon third-party identifiers. Amperity does not have a dedicated Sync Injector.

Additional Amperity Documentation

Amperity - Streaming Ingest API

Updated 4 months ago