Convert

📘

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

What Is Convert?

Convert is a versatile software tool designed for businesses to optimize their digital marketing efforts. It offers a suite of features including A/B testing, split URL testing, and multivariate testing to improve website performance and conversion rates. Convert provides intuitive, user-friendly interfaces for setting up experiments, tracking results, and making data-driven decisions, helping businesses to refine their online strategies and maximize conversions effectively.


Product Type: Analytics
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Full-Funnel Events


Capabilities

  • Streams server-side event data into Convert for experiment tracking and measurement.
  • Unlocks all customer data events and attributes for custom event mapping and transformation.
  • Has no effect on website load latency.
  • Supports full-funnel events including page, product, cart, and order lifecycle actions.

Considerations

  • The account ID and project ID are available in your Convert account URL.
  • Each event's ev output specifies the Convert event type(s) to send. By default most events send hitGoal; order_completed sends both hitGoal and tr (transaction). To change which types are sent for an event, modify eventTypes in that event's mapping (e.g., {"hitGoal"} for just hitGoal, or {"hitGoal", "tr"} for both).
  • Transaction (tr) events include the order revenue (r) and ordered product count (prc).
  • Events are only sent when the conv_v value is present; events without it are filtered out.
  • Screen events are not supported and are filtered out.

Identity Sync

Sync Details

  • Captures the conv_v value used for session identification and experiment bucketing.
  • Required by Convert to associate events with a user's session, variations, and segments.
  • Without this sync, events may not be accepted as valid by the integration.

Starter Kit Setup Guide

1. Deploy the Convert Sync

  • To collect the sync values (e.g., conv_v), you must implement a Convert ID sync. Refer to the following documentation to complete the setup: Convert - ID Sync Guide.

2. Gather Credentials

  • Gather the following IDs from your Convert account:
    • Account ID: Found in your Convert account URL (e.g., app.convert.com/accounts/XXXXXXXX/).
    • Project ID: Found in the project list on the homepage, or in the URL once you click into a project (e.g., app.convert.com/accounts/XXXXXXXX/projects/XXXXXXXX).

3. Add a Convert Integration

  • From the integration library, add a Convert integration. Then, fill out the Connection Parameters:
Connection ParameterDescription
PROJECT_IDThe project ID.
ACCOUNT_IDThe account ID.

4. Configure Event Mapping

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

5. Deploy to Pipeline

  • In the Pipelines tab, add your Convert 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 KeyDescriptionExpected Input
cid RequiredString: Account ID.$$ACCOUNT_ID$$
pid RequiredString: Project ID.$$PROJECT_ID$$
tid RequiredString: Transaction ID, used for deduplication.messageId
seg.browserString: Browser derived from user agent. One of IE, CH, FF, OP, SF, OTH.Expression – derives the browser code from context.userAgent
seg.devicesString: Device, one or more of DESK, OTHDEV, IPAD, ALLTAB, OTHTAB, OTHPH, IPH, ALLPH.Expression – derives device from context.device.type
seg.sourceString: One of direct, referral, Search, Campaign.Expression – returns the traffic source
seg.newBoolean: 0 if a new visitor in this session, 1 if returning.Expression – derived from conv_v page views
seg.ctryString: Two-letter ISO country code.Expression – converts context.location.country to ISO code
seg.custString: Array of custom audience IDs set up in the project as segments.Expression – parsed from conv_v segments
vid RequiredString: Session ID.messageId

Event Specific

Every event maps the ev output using the same expression; order_completed is the only event that sends a transaction (tr) in addition to hitGoal.

Identify

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Page

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Products Searched

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Product List Viewed

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Product Viewed

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Product Added

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Payment Info Entered

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Cart Viewed

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Checkout Started

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Promotion Clicked

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal), goals, variation IDs (vars), and experience IDs (exps).Expression – builds the event array from conv_v

Order Completed

Output KeyDescriptionExpected Input
evArray: Builds the list of Convert events to send — for each experiment the user was bucketed into, an entry with the event type (hitGoal and tr), goals, variation IDs (vars), and experience IDs (exps). Transaction entries also include order revenue (r) and ordered product count (prc).Expression – builds the event array from conv_v, including transaction data

Required & Recommended Identifiers

These identifiers must be mapped to Convert in order for successful user matching to occur. Without these IDs, any events sent to Convert 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?
vid Required1588166554499-0.2020703998482254Yes
seg.browser RecommendedCHNo
seg.devices RecommendedDESKNo
seg.source RecommendeddirectNo
seg.new Recommended1No
seg.ctry RecommendedRONo
seg.cust Recommended123No

Integration Validation

Coordinate with your Convert representative to confirm that events are being received and processed correctly on their backend.


Additional Convert Documentation