Back to jobs

Wire respond.io to Meta Conversions API: fire Lead/Purchase events from CRM lifecycle changes

Search - API Integration · local_filter_skipped · UID ~022079709339176190416

Open Job

Job Details

Budget Unknown
ExperienceExpert
DurationUnknown
Weekly hoursUnknown
Client countryUnknown
ProposalsUnknown
InterviewingUnknown
Invites sentUnknown
First seenTue, Jul 21, 2026 11:46 PM
Last seenWed, Jul 22, 2026 8:47 AM

Description

NOT LOOKING FOR SOMEONE TO RUN CAMPAIGNS OR ADS FOR US, WE ALREADY DO SO. AND NOT LOOKING FOR SOMEONE TO SET UP RESPOND.IO WORKFLOWS, WE CAN DO THAT OURSELVES. We want a developer to build a custom pipeline using the respond.io API that reports our qualified leads to Meta through the Conversions API, so our campaigns optimize toward real buyers. How our funnel works: We run Meta lead campaigns where the ad's goal is to get people into Facebook Messenger. All of our selling happens inside Messenger. We do not collect phone numbers or emails, and we don't send anyone to a website. Our team messages and segments every lead inside respond.io (our CRM), and when a lead gets serious we move them through lifecycle stages (Hot Lead, then Payment when they buy). The problem: Meta has no idea any of this is happening. The campaign has spent about $1,800 and produced 1,500+ qualified leads by our count, but Meta's reporting shows only a handful of conversions because all it sees is "conversation started." It never learns which conversations became real leads and paying customers. So the algorithm optimizes for people who like to start chats, not people who buy. What we have: Full access to respond.io's API and webhooks, admin access to our Meta Business Manager, and a dataset in Events Manager. The plumbing exists on both ends. We want someone to build the middle. What we want built: A custom pipeline where every lifecycle change to Hot Lead or Payment in respond.io automatically fires

Skills

API Web Development

Notification History

ChannelTypeStatusSentError
No notifications.

User Actions

ActionActed at
No actions.