CRM data integration

CRM integration lets a campaign tool pass viewer-specific data into a Blings MP5 experience using the same personalization fields already used in email, SMS, push, and landing-page workflows.

Start in Platform Integration

Before editing a CRM template, open the project in Platform Integration and collect the generated instructions:

Integration

Use Integration to:

Confirm the Dynamic Data field names.
Save the Landing Page settings and selected lineup.
Copy the generated CRM Integration URL.
Copy the Dynamic Thumbnail URL if the email or message includes a personalized thumbnail.
Run an end-to-end CRM test after replacing sample values with the CRM's merge-tag syntax.

Use Simulation separately to preview representative viewer profiles before the campaign send.

Simulation

Video Context

Field

Details

Summary

Explains how CRM data can be passed into Blings through URL parameters, merge tags, or a personalized landing page so each viewer sees a data-driven MP5 experience.

Target audience

CRM administrators, marketing operations, lifecycle teams, solution architects, and developers planning a Blings launch through email, SMS, or a CRM landing page.

Approximate duration

4:55

Watch this when...

You are deciding how to connect CRM fields to a Blings video, preparing an ESP campaign, or aligning technical and campaign teams on the integration approach.

CRM Integration Patterns

Most CRM and ESP tools support merge tags in links. Copy the generated CRM URL from Platform, then replace the sample values with the CRM tokens for the same fields.

Example:

https://mycompany.mp5.live/onboarding?first_name={{ contact.firstname }}&plan={{ contact.plan }}

When the recipient clicks the link, the CRM resolves the merge tags and the MP5 receives the values as URL parameters.

Use this pattern when:

The campaign is sent by email, SMS, push, or another CRM-owned channel.
The required fields are short enough to pass in a URL.
The data is acceptable to include in a link after applying your privacy and security rules.
You need the fastest path from Platform instructions to a live CRM campaign.

CRM URL parameters mapped into a Blings personalized video link

URL Parameters as Compact Token-Based Approach

Use a CRM-hosted landing page when the CRM or ESP should own the page URL, consent experience, template, analytics wrapper, or data injection.

The CRM page renders its own merge tags, creates a data object, and initializes the Blings player.

<script>
  const data = {
    first_name: "{{ contact.firstname }}",
    plan: "{{ contact.plan }}"
  };

  BlingsPlayer.create({
    project: { id: "project-id-from-platform" },
    settings: {
      container: document.getElementById("blings-video-container")
    },
    data
  });
</script>

Use this pattern when:

The CRM should host the page, such as Salesforce Marketing Cloud CloudPages or Marketo landing pages.
The data should not appear in the URL.
The page needs CRM-specific tracking, consent controls, or page personalization before the player loads.
The campaign team wants a branded page around the MP5 experience.

CRM landing page passing personalized data into the Blings player

Common CRM Merge-Tag Syntax

CRM syntax changes by platform. Keep the parameter name from Blings and use the CRM's syntax for the value.

Platform

Example value syntax

HubSpot

{{ contact.firstname | default("there") }}

Salesforce Marketing Cloud

%%FirstName%%

Marketo

{{lead.First Name:default=there}}

Klaviyo

{{ first_name|default:"there" }}

Braze

{{${first_name} | default:'there'}}

Iterable

{{firstName}}

Mailchimp

*|FNAME|*

Generic CRM

Use the tool's merge tag for the mapped contact, account, event, or custom object field.

QA Checklist

Simulate the profile in Platform using values that match the CRM test contact.
Send a real test message from the CRM, not only a template preview.
Open the generated link and confirm the CRM resolved all merge tags.
Confirm the MP5 shows the expected text, media, routing, links, and interactive actions.
If using a Dynamic Thumbnail, confirm the thumbnail and MP5 use the same viewer values.
Check default values for contacts with missing fields.
Check URL encoding for spaces, special characters, non-English text, and long values.

Need help configuring your CRM integration? Contact us.

Last updated 1 month ago