> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/videos/implementing-blings-with-your-crm.md).

# Implementing Blings with Your CRM

Use this video to understand the CRM integration patterns that let Blings personalize video experiences with the data and merge-tag logic your team already uses.

{% embed url="<https://assets.blings.io/helpcenter/Implementing%20Blings%20with%20Your%20CRM.mp4>" %}

## 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.       |

## Key takeaways

* Blings can use the same CRM personalization fields already used in email and landing-page workflows.
* URL parameters are a direct way to pass viewer data into the video experience.
* Personalized landing pages give teams more control when the CRM or web layer should prepare the data before player initialization.
* A single MP5 template can support many personalized outcomes without creating separate rendered MP4 files.
* Test with representative CRM values before launch so empty fields, defaults, and encoded links behave as expected.