Integrations help

Supported channels and where to start

Open Integrations in the business workspace. Current supported channels are Website Form, Google Ads, Meta Ads, WhatsApp and Email / SMTP. Permissions and platform readiness determine which controls are available.

Spreadsheet Capture and CSV Import are separate input workflows, not additional third-party integration promises. Use Import for a one-time CSV migration and Spreadsheet Capture for ongoing supported spreadsheet input.

Connection status and readiness

A provider can also report health, last sync or last error. Missing platform configuration is not fixed by repeatedly entering customer credentials. Contact support when the connection action reports that setup is unavailable.

Connecting Google Ads

The integration reads account, campaign performance, attribution and supported lead-form data. It does not edit your ads. Unselected or inaccessible accounts will not contribute the expected sync data.

1. Open Google Ads in Integrations and start Direct Connect.
2. Approve the official Google permission screen using an account that can access the intended advertising accounts.
3. Select at least one discovered account for synchronization and confirm the selection.
4. Review account/campaign mapping and the last sync result. Use the available sync action once where appropriate.

Connecting Meta Ads

1. Open Meta Ads and start Direct Connect.
2. Approve Meta permissions for the intended business and advertising accounts.
3. Select discovered accounts to synchronize; confirm source/campaign mapping.
4. Review last sync, enabled state and safe errors before comparing source spend.

Connecting and using WhatsApp

The current runtime supports one active connected business number. Free-form conversation replies require the open 24-hour customer-service window; outside it, use an approved template where allowed. A sent message is not necessarily delivered or read.

Meta WhatsApp usage charges are billed separately by Meta to your connected WhatsApp Business Account. RevenueLancer does not add a markup to Meta messaging charges.

1. Open WhatsApp and choose Connect WhatsApp.
2. Approve the official Meta flow for your business-owned WhatsApp account. The connection discovers the available number; ordinary setup does not ask you to paste private provider tokens.
3. Review connection readiness, number and safe status. Check the communication tool’s permission before sending.
4. Use permitted messages or approved templates and inspect delivery history/status for the actual result.

Business Email / SMTP

Business-owned channels are distinct from RevenueLancer’s platform account/security and Contact emails. The integration is SMTP-based; it is not a promise of a synced mailbox or inbox-reading connector.

1. Open Email / SMTP and use a business-owned SMTP account.
2. Enter the host, port, encryption mode, username, password and permitted From address; set Reply-To where offered.
3. Save, then use Test email / connection and inspect its result. Do not expose the saved password in screenshots.
4. Use the approved notification or communication action available in the product; check logs rather than assuming SMTP acceptance means inbox delivery.

Website Form and first-party capture

Native Lead Capture forms are a separate first-party capture interface. Check form defaults and required fields before sharing. Do not assume an arbitrary website field will be mapped automatically.

1. Open Website Form in Integrations and enable the supported webhook setup.
2. Generate/configure the webhook secret and use the endpoint shown in the app.
3. Send the supported JSON submission from a trusted server using x-revenuelancer-webhook-secret; never expose the secret in public browser code.
4. Test one clearly identifiable enquiry, then verify the lead, source and ownership inside RevenueLancer.

Logs, delayed sync and duplicate checks

Use the available connection/test/sync logs and safe error summaries to identify whether the failure happened at connection, selection, synchronization or lead creation. Compare timestamps with the period you are reviewing.

If leads do not arrive, confirm the actual channel supports ingestion—Meta Ads aggregate sync is not a lead capture path. For duplicates, inspect whether the same source was connected through more than one input workflow.

Disconnecting and reconnecting safely

Review the disconnect dialog before confirming. Ads connections offer preserving history or deleting provider history; canonical leads are preserved by those provider-disconnect paths. These choices are not interchangeable.

WhatsApp disconnect preserves message history while removing the active connection. Reconnect through the official provider flow and recheck account/number selection and mapping. Do not delete history as a generic fix for an expired connection.