Yonatan Schreiber | Oct 22, 2026
When a marketing team hears “integration,” they often picture an engineering ticket: an API build, a sprint, and a quarter of waiting. For personalized video, that picture is wrong in most cases. If you can add a merge tag to a link, you can deploy a Smart Video.
This post explains what CRM integration actually involves, what it does not, and the rare cases where a developer needs to be in the room.
The core of Blings CRM integration is the Smart Video Link: a single URL you paste into a campaign you are already sending. You attach your CRM’s merge tags to it, the same tags you use to put a first name in a subject line. When the message sends, the CRM fills in the values, and the Smart Video reads them.
There is no data pipeline to maintain and no file to produce for each contact. The video is generated on the recipient’s device at the Moment of Open, so your work ends at pasting a link and mapping a few fields.
Blings supports a short menu of integration patterns. Most teams never go past the first one.
| Pattern | Use it when | Who sets it up |
|---|---|---|
| Merge tags in the Smart Video Link | You send through email, SMS, push, or any CRM campaign and can place a merge tag in a link | A marketer, in the campaign editor |
| CRM-hosted landing page | The CRM should own the page, the consent layer, or the tracking, or the data should not appear in the URL | A marketer with light help from a web or CRM admin |
| SDK or custom API | Personalization depends on backend logic, a CDP, authentication, or live product state assembled at the moment of the request | A developer |
The first row covers the large majority of lifecycle and marketing campaigns. The API only enters the picture when data has to be assembled by a system at request time, which is the exception, not the rule.
This is what Zero Tech Debt means in practice: nothing new to run, patch, or hand off to engineering after launch.
Most teams complete this in a single sitting. Nothing here requires a release cycle.
There is a real line, and it is worth naming honestly. Bring in a developer when the personalization depends on data that does not exist as a simple CRM field: a live account balance pulled at request time, a recommendation assembled by a CDP, or content behind authentication. In those cases, the Blings SDK or a custom API lets your system pass a data object straight to the player. Everything short of that is a marketer’s job.
Not for standard campaigns. For email, SMS, and push, you add merge tags to the Smart Video Link in your CRM. An API or the SDK is only needed when data is assembled at runtime by a backend or CDP.
Most teams finish in one sitting: confirm the field names, copy the Smart Video Link, add your merge tags, paste it into a campaign, and run one test send.
Usually no. The merge-tag pattern is done entirely in your CRM campaign editor. A developer is only needed for backend or CDP-driven personalization.
No. You keep working in your current CRM, using the merge tags you already know. There is no new system to learn.
It means there is nothing new to run or maintain after launch. Blings adds no pipeline, no per-customer files, and no change to your CRM as the source of truth.
