Amperity
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 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 analytics tools that help businesses gain insights into customer behavior, preferences, and trends, ultimately driving better decision-making and more targeted marketing strategies.
Product Type: Customer Data Platform
Integration Type: Starter Kit
Event Source Type: Web
Event Scope: Full-Funnel Events
Capabilities
- Sends server-side event data to Amperity, eliminating the need for an Amperity tag on the site and reducing client-side overhead.
- Centralizes data collection and routing through MetaRouter for consistent data quality.
- Delivers events and identifiers to Amperity's Streaming Ingest API.
- Passes the
context.providersobject so identifiers gathered by the Sync Injector can power downstream functionality.
Considerations
- Authentication uses a Bearer write access token supplied by Amperity.
- The tenant ID is sent both in the endpoint and in the
X-Amperity-Tenantheader and must match the value provided by Amperity. - The stream ID identifies the Streaming Ingest destination and must match the value provided by Amperity.
- Amperity does not have a dedicated Sync Injector. The
context.providersobject may still contain identifiers gathered by other syncs, which should be mapped in the appropriate integrations. - Required identifiers must be present on every event or events sent to Amperity will be rejected.
Starter Kit Setup Guide
1. Gather Credentials
- Ask Amperity representatives for the following credentials:
- Tenant ID
- Write access token
- Stream ID
2. Add an Amperity Integration
- From the integration library, add an Amperity integration. Then, fill out the Connection Parameters:
| Connection Parameter | Description |
|---|---|
TENANT | A unique identifier assigned to a specific organization or instance of the Amperity platform. |
TOKEN | Write access token. |
STREAM_ID | A unique identifier assigned to a specific data stream used for data ingestion within the Amperity platform. |
3. Configure Event Mapping
- 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.
4. Deploy to Pipeline
- In the Pipelines tab, add your Amperity integration.
- Select the correct integration revision.
- Click Add Integration to finalize deployment.
Event Mappings
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 |
|---|---|---|
messageId Required | String: ID used to identify a single event. | messageId |
anonymousId Required | String: Persistent, unique identifier (like a UUID) for an unauthenticated user, used for tracking and attribution. | anonymousId |
userId Required | String: Persistent, unique identifier (like a hashed email or database ID) for an authenticated user, used for tracking and attribution. | userId |
originalTimestamp Required | String (ISO 8601): The original timestamp of the event. | originalTimestamp |
timestamp Required | String (ISO 8601): The timestamp when the event was recorded. | timestamp |
context.userAgent Required | String: The user agent string of the device. | context.userAgent |
context.providers | Object: May contain identifiers gathered by the Sync Injector, to be mapped in the appropriate integrations for downstream functionality. | context.providers |
traits Required | Object: Key-value pairs describing the user, such as email, name, and age. | traits |
event Required | String: The event type; track events are lowercased with spaces replaced by underscores. | Expression – transforms input.event or returns input.type |
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.
| Attribute | Example | Sync Injector Required? |
|---|---|---|
messageId Required | abc123def456ghi789 | No |
anonymousId Required | 130161d0-8fee-4167-aa4d-d151eed27c6b | No |
userId Required | user-5678-wxyz-1234-abcd | No |
userAgent Required | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 | No |
context.providers Recommended | {"google_analytics":{"gclid":"1234567890.1234567890"}} | Yes* |
traits Required | {"email":"[email protected]","name":"John Doe","age":30} | No |
*Depending on your configuration, the context.providers object may contain identifiers gathered by the Sync Injector. These should be mapped in the appropriate integrations to power downstream functionality reliant on third-party identifiers. Amperity does not have a dedicated Sync Injector.
Integration Validation
- Coordinate with your Amperity representative to confirm that events are being received and processed correctly on their backend.
Additional Amperity Documentation
Updated 5 days ago