Integration
Collect project-specific delivery URLs, thumbnails, custom code, spreadsheet outputs, and SDK instructions in Platform Integration
Integration is the Platform area for delivery setup. Use it to collect the generated landing page URL, CRM link format, dynamic thumbnail URL, custom code, spreadsheet output, or SDK details for the project.
Integration does not test viewer data or rendered personalization. Use Simulation when you need to preview the MP5 with representative profiles.

What Integration Provides
Use Integration to review and copy:
Landing Page settings, including URL alias, selected scene lineup, page title, page description, social thumbnail, and preview link.
Dynamic Thumbnail setup for personalized image or GIF delivery in email, messaging, and share surfaces.
Custom Code for hosted-page customization, direct embed behavior, or implementation-specific JavaScript.
Integration Methods for CRM links, Spreadsheet or CSV delivery, and SDK implementation details.

Integration Types
Blings-hosted landing page with URL parameters
You are sending through email, SMS, push, or a CRM campaign and can place merge tags in the link.
Landing page URL, selected lineup, CRM Integration URL format, required parameter names.
Dynamic thumbnails
You want personalized email or messaging thumbnails that match the viewer data used by the MP5.
Dynamic thumbnail URL, thumbnail parameter mapping, and the final click-through URL.
Spreadsheet or CSV
You need a manual send, controlled test batch, data upload, or one-time campaign without a live system.
Spreadsheet/CSV instructions, sample file format, key column, and matching project fields.
CRM-hosted landing page
The CRM or ESP should host the page and inject personalization into the page before the player loads.
Landing page settings, custom code or HTML output, field names, and selected lineup.
Custom HTML page
You want to host the player on your own web server while using Blings project configuration.
Custom Code or HTML output, project ID, selected lineup, SDK initialization details.
SDK or custom API
Your website, app, backend, CDP, or product needs to assemble data at runtime and pass JSON into the player.
SDK tab details, project ID, field schema, scene or lineup information, and any required settings.
Mobile WebView
A native iOS or Android app should open the hosted MP5 page or a custom SDK page inside the app.
Hosted page URL or custom page URL, supported query parameters, and any Advanced custom JavaScript.
How to Choose
Fastest campaign launch from a CRM or ESP
Blings-hosted landing page with CRM merge tags in URL parameters.
Email needs a personalized preview image or GIF
Add Dynamic Thumbnail to the CRM or ESP template.
One-time campaign, proof of concept, or offline list
Spreadsheet or CSV.
CRM must own the page URL, consent layer, or page template
CRM-hosted landing page.
Data is sensitive or should not appear in a URL
SDK/custom API or CRM-hosted landing page with data injected into the page.
Personalization depends on backend logic, CDP enrichment, authentication, or live product state
SDK/custom API.
Same MP5 must appear inside a mobile app
Hosted page or SDK page inside a WebView.
The experience needs custom JavaScript on the hosted page
Integration custom code or the SDK page that your team hosts.
Get Instructions Correctly

Follow this order when preparing instructions for a CRM owner or developer:
Confirm the project and environment. Do not copy links, IDs, code, or parameter names from another project.
Open Settings -> Dynamic Data and confirm the exact field names the MP5 expects.
Open Integration -> Landing Page and confirm the URL alias, selected lineup, page title, page description, social thumbnail, and preview link.
Save landing page changes before copying generated links or code.
Open the correct Integration Methods tab: CRM Integration, Spreadsheet (CSV), or SDK.
Copy the generated output from Platform, then replace sample values only where the target system requires its own merge-tag syntax or JSON data source.
If using Dynamic Thumbnail, copy the thumbnail URL after the main video URL and parameter mapping are stable.
Send the implementation owner the chosen method, generated output, required fields, fallback expectations, and the relevant Developer and Integration article.
Run an end-to-end test from the delivery system.
For CRM and ESP links, parameter names should match the project Dynamic Data fields. Parameter values should use the CRM's merge-tag syntax, such as a contact first name token, account tier token, or offer token.
Related Developer and Integration Guides
How to connect my data to the videoCRM data integrationCustom API IntegrationLast updated

