iHeartMedia - Magellan
Step-by-step guide to integrate Ours Privacy with iHeartMedia - Magellan for sending events via their tracking API while maintaining privacy and compliance.
iHeartMedia - Magellan
The iHeartMedia - Magellan destination allows you to send events to Magellan's tracking API at https://mgln.ai. Events are sent to event-specific URLs based on the event name (e.g., https://mgln.ai/view, https://mgln.ai/purchase, https://mgln.ai/lead).
Overview
This integration enables you to track conversions and user behavior from your audio advertising campaigns through Magellan's tracking endpoint. The destination automatically routes events to the appropriate endpoint based on your event names, making it easy to track different types of conversions and user actions.
Use Cases
- Track conversions from audio advertising campaigns
- Monitor user engagement with iHeartMedia ad content
- Optimize audio advertising performance with conversion data
- Measure ROI from iHeartMedia advertising investments
- Track page views, purchases, and lead generation events
Requirements
- A Magellan account with access to tracking
- A unique pixel token provided by Magellan
Setup
Getting Your Token
To set up the Magellan destination, you'll need to obtain your unique pixel token:
-
Access Your Magellan Account:
- Log into your Magellan account
- Navigate to your tracking or pixel settings
-
Retrieve Your Token:
- Locate your unique pixel token in your Magellan dashboard
- Copy the token for use in Ours Privacy
-
Configure in Ours Privacy:
- Enter your token in the destination settings
- Configure event mappings for the data you want to send
Configuration
Settings
- Token (Required): The unique pixel token provided by Magellan for your events. This token is used to authenticate and link events to your account.
Event Mapping
The Magellan destination supports flexible event mapping to match your tracking needs:
Required Fields
- Event Name: The name of the event. This determines the URL endpoint (e.g.,
view,purchase,lead). Supports event renaming to match Magellan's expected event types.
Optional Fields
- Event Properties: An object containing additional event properties that will be included in the payload. All properties from this object will be spread into the JSON payload sent to Magellan.
How is this guide?