myTarget Integration with Bitrix24: Lead Import, Audience Sync & Offline Conversions

A marketer runs campaigns in myTarget, collects leads through Lead Ads, exports them daily from the cabinet, and manually enters them into the CRM. By that time, some leads have cooled off, some have been lost in forwarding between colleagues. Campaign costs are calculated in a separate spreadsheet, and the link "click → lead → deal → payment" exists only in the marketer's head. We offer integration of myTarget with Bitrix24 that closes this loop: leads enter the CRM automatically, costs are imported, and audiences are updated from CRM segments. Our experience shows that after integration, lead processing time is reduced by 70%, and ROI of advertising campaigns increases by 15–25% due to quality attribution and offline conversions.

myTarget Lead Ads and Automatic Import

myTarget allows creating Lead Ads (Lead Ads) — the user leaves a request in the Odnoklassniki feed or on Mail.ru platforms without transitioning to an external site. The form data is stored in the myTarget cabinet and accessible via API.

Integration works through myTarget API v2:

1. The user fills out a Lead Ad on a myTarget platform.
2. Bitrix24 periodically polls the myTarget API (or accepts a webhook if configured) and retrieves new submissions.
3. For each submission, a lead is created in the CRM with populated fields: first name, phone, email, data from custom form fields.
4. An assignee is set, and first-stage robots are triggered.

Server-side integration is used — the application authorizes in myTarget via OAuth 2.0, receives an access token, and requests data via GET /api/v2/lead_ads/vk_forms.json.

Field Mapping

Lead Ad fields from myTarget need to be mapped to Bitrix24 CRM fields. Typical mapping:

If the myTarget form has hidden fields with UTM tags — they are passed to the lead and populate the standard fields UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN.

How to Upload Audience from CRM to myTarget?

myTarget accepts audiences for targeting via Audiences → User Lists. Data is uploaded as hashes of phone numbers and emails. Bitrix24 can form such lists from CRM segments.

Typical scenarios:

• Look-alike based on buyers. Segment "Deals with status 'Successfully closed' in the last 12 months" → hash export → myTarget builds a similar audience.
• Retargeting warm leads. Segment "Leads with status 'In progress', no activity for 7 days" → follow-up advertising on Mail.ru and OK platforms.
• Exclude clients. Segment of current clients → exclude from acquisition campaigns.

Export is implemented via CRM Marketing → Audiences in Bitrix24. Data is hashed (SHA-256) before sending — only hashes, not raw data, go to myTarget.

For automatic audience updates, regular synchronization is configured: when a segment changes in the CRM, new contacts are added to the myTarget audience, removed ones are excluded.

Import of Costs from myTarget

The myTarget API provides campaign statistics via GET /api/v2/statistics/campaigns/day.json. Bitrix24 retrieves:

• Daily costs per campaign and ad
• Impressions, clicks, CTR, CPC
• Conversion data (if tracking is configured)

In Bitrix24's end-to-end analytics, myTarget costs are matched with leads and deals based on UTM tags. The report shows the full picture: campaign spend → number of leads → deal conversion rate → revenue → ROI.

For correct attribution, all links in myTarget ads must contain UTM tags. Recommended format: utm_source=mytarget&utm_medium=cpc&utm_campaign={campaign_id}. myTarget macros ({campaign_id}, {banner_id}) automatically substitute the campaign and ad ID.

Why Connect Offline Conversions?

myTarget supports offline conversions — passing events from the CRM back to the advertising cabinet. This allows optimizing campaigns based on actual sales rather than clicks. In practice, this approach yields a 30–50% increase in efficiency compared to regular click-based optimization.

Scheme:

1. A [email protected] counter is created in myTarget and a conversion goal is set.
2. When a deal is closed in Bitrix24, a robot on the "Successfully closed" stage sends a conversion event via the myTarget API (POST /api/v2/remarketing/conversions.json).
3. myTarget matches the conversion with the click based on user_id or hash of contact data.
4. myTarget algorithms begin optimizing ad delivery toward audiences more likely to make a purchase.

For conversion transfer, a click_id link is needed (passed as a GET parameter when clicking on the ad) and the CRM event. The click_id is saved in a custom lead field upon creation, then used when sending the conversion.

Comparison of myTarget and VK Ads

myTarget and VK Ads are different advertising platforms (though both belong to VK). The APIs are different, data formats differ, and audiences partially overlap. If you advertise on both platforms — you need two separate integrations. In Bitrix24's end-to-end analytics, they will appear as different sources.

What the Work Includes

• Connecting the myTarget cabinet to Bitrix24 via OAuth 2.0 and setting up synchronization
• Automatic import of leads from myTarget Lead Ads into the CRM
• Mapping form fields to CRM fields, creating missing custom fields
• Setting up audience upload from CRM segments to myTarget
• Importing costs and connecting to end-to-end analytics
• Tagging ad campaigns with UTM tags using myTarget macros
• Configuring offline conversion transfer from CRM to myTarget
• Testing the full chain: click → Lead Ad → lead in CRM → UTM → costs → conversion
• Integration documentation and training for your employees
• 30-day warranty on the work after delivery

We will evaluate your project for free — just drop us a message. The integration is delivered turnkey with a fixed timeline and no hidden extras.