FAQ
Transferring leads from Facebook via Albato
Facebook Lead Ads Integration via Albato
- What You Need to Prepare Before Getting StartedAn Albato account (albato.ru)
- A personal Facebook account with administrator permissions for the Page where the Lead Ads forms were created
- A published Lead Ads form (not a draft) — see the separate guide on creating one via Ads Manager
- An API key from your onecrypt.link profile — https://onecrypt.link/u/profile
- The offer ID in onecrypt.link associated with the advertising campaign
Part 1. Connecting Facebook to Albato Step 1. Select the Facebook ServiceIn Albato, go to Connections → Add a Connection, then search for Facebook.
Several options will appear in the list. Select the first one, simply called Facebook* (not Conversions API, Pages, or Audiences). Those integrations are intended for other purposes and are not used to receive leads.
Step 2. Name the Connection
Enter a clear, descriptive name, for example, “My Facebook Account”, and click Next.
Enter a clear, descriptive name, for example, “My Facebook Account”, and click Next.
Step 3. Grant Access
Facebook will warn you that if you change your account password, the connection will be disconnected and you will need to reconnect it. This is normal—just keep it in mind for the future.
Click “Grant Albato Access” and sign in with the Facebook account that has administrator permissions for the required Page.
Facebook will warn you that if you change your account password, the connection will be disconnected and you will need to reconnect it. This is normal—just keep it in mind for the future.
Click “Grant Albato Access” and sign in with the Facebook account that has administrator permissions for the required Page.
Step 4. The Connection Is Ready
Once authorization is complete, click “Create Automation.”
Once authorization is complete, click “Create Automation.”
Part 2. Creating an Automation with a Lead Ads Trigger
Step 5. Start with a Blank Automation
The automation builder will open. Click the “Add a Trigger” block — this is the event that will start the entire workflow.
Step 5. Start with a Blank Automation
The automation builder will open. Click the “Add a Trigger” block — this is the event that will start the entire workflow.
Step 6. Find Facebook Among the Sources
Enter Facebook in the search bar. You will see four similar options in the list. Select the first one, simply called “Facebook.”*
Enter Facebook in the search bar. You will see four similar options in the list. Select the first one, simply called “Facebook.”*
- Facebook* — receives data from Facebook (leads, etc.) — select this one
- Facebook Conversions API* — sends events to Facebook (the opposite direction) — not suitable
- Facebook Pages* — used for Page-related actions (posts, messages) — not suitable
- Facebook Audiences* — uploads contacts for ad targeting — not suitable
Select the “Leads from Forms (Webhook)” event, choose the account connection you created in Part 1, then select the required Facebook Page and the specific Lead Ads form.
Click “Continue.”
Step 8. Set the Automation Mode
Select “Real Time” (collect data from the current period). This ensures that the automation captures new leads as they come in, rather than importing historical data as a one-time batch.
Click “Save.”
Select “Real Time” (collect data from the current period). This ensures that the automation captures new leads as they come in, rather than importing historical data as a one-time batch.
Click “Save.”
Part 3. Testing the Trigger
Step 9. Run the Test
Albato will prompt you to test the trigger. Click “Test.”
Step 9. Run the Test
Albato will prompt you to test the trigger. Click “Test.”
Step 10. Wait for the Webhook
Click “Wait for Webhook” and, while this window is open, submit a test lead through the Facebook form itself (using the ad preview or the Lead Ads Testing Tool).
Click “Wait for Webhook” and, while this window is open, submit a test lead through the Facebook form itself (using the ad preview or the Lead Ads Testing Tool).
Step 11. Check the Received Data
After submitting the test lead, Albato should display the captured data: Page ID, Form ID, Form Name, Lead ID, Creation Date, and the lead fields themselves (in our test, Full name and Phone number were received).
Click “Continue with Selected Data.”
After submitting the test lead, Albato should display the captured data: Page ID, Form ID, Form Name, Lead ID, Creation Date, and the lead fields themselves (in our test, Full name and Phone number were received).
Click “Continue with Selected Data.”
Part 4. Configuring Lead Submission to cpa.tl
Step 12. Add the “Send Request” Action
Add the next step to the automation: “HTTP Request / Outgoing Webhook” → “Send Request.”
For the connection, select the previously created “Send to cpa.tl” connection (the same one used in the landing page guide — there is no need to create it again).
Step 12. Add the “Send Request” Action
Add the next step to the automation: “HTTP Request / Outgoing Webhook” → “Send Request.”
For the connection, select the previously created “Send to cpa.tl” connection (the same one used in the landing page guide — there is no need to create it again).
Шаг 13. Заполняем параметры запроса
Метод — POST (уже проставлен по умолчанию из подключения). Урл можно оставить пустым — он подставится из настроек подключения. Дальше заполняем параметры:
Метод — POST (уже проставлен по умолчанию из подключения). Урл можно оставить пустым — он подставится из настроек подключения. Дальше заполняем параметры:
key | String | API key from your onecrypt.link profile (static — the same for all leads) |
name | String | Full name field from the Facebook webhook data (dynamic) |
phone | String | Phone number field from the Facebook webhook data (dynamic, required) |
country | String | country code — static (the screenshot uses GT as an example; enter the appropriate value for your campaign) |
offer_id | Int | offer ID for the campaign/form receiving the traffic (static — specific to each campaign) |
ip_address | String | static placeholder value 0.0.0.0 (required — see the warning at the beginning of this document) |
Required fields according to the onecrypt.link API specification: key, offer_id, phone, ip_address. Without these fields, the lead will not be accepted.
Save the parameter settings.
Final CheckThe integration is now ready. Submit another test lead through the Facebook form and verify the entire workflow:
Save the parameter settings.
Final CheckThe integration is now ready. Submit another test lead through the Facebook form and verify the entire workflow:
- In Albato: check the automation run history. Both steps (the Facebook trigger and the HTTP request) should complete without errors. The HTTP request should return HTTP 200 and a JSON response containing the lead ID.
- In onecrypt.link: make sure the test lead appears in the system. The easiest way to find it is by searching for the phone number used in the test.
- If everything was received successfully, you can leave the automation enabled for continuous operation.
- Common IssuesNo administrator permissions for the Page containing the forms — this is the most common cause of Facebook integration issues.
- The lead form is still in draft status — Albato will not display it in the list until the ad containing the form has been published. You do not need to actually start delivering the ads; you can pause the campaign immediately after publication.
- No test data is received while “Wait for Webhook” is active — make sure the test lead is submitted through the exact form selected in Step 7, and that the webhook waiting window is still open when the lead is submitted.
- The lead was received without a name or phone number — make sure these questions are included and enabled in the Facebook form.
- “Invalid IP address” error from onecrypt.link — make sure the ip_address parameter contains the agreed placeholder value 0.0.0.0 rather than being left empty.