Send the outcome. Check what the ad platform heard.

Agree what contacted, qualified and won mean with the advertising and enquiry teams before sending stage changes outside Kibi. An interested person is not automatically a customer, and an unanswered enquiry is not automatically unsuitable. Clear definitions give teammates a consistent reason to update a record and let the ads administrator understand the outcomes being reported. Start with your actual sales process rather than a target number of conversion events.

Ad signals are included on Growth and during the eligible trial. Use an account with the Connect Meta and Google ads permission and authorised provider access. If controls are unavailable, check the workspace permission and plan, then provider access. Ask the account administrator to grant access through the normal process rather than sharing a login.

Meta outcome signals · Available. Google conversions · Available. These describe outcome feedback, which is separate from bringing enquiries into Kibi or importing ad spend. Facebook & Instagram lead ads · Beta — Available after a short review; Google lead forms · Coming. A working Google conversion connection therefore does not mean Google lead forms are ready to receive enquiries. Start this guide with the source your team actually uses and the advertising account that should receive its results.

For the Meta setup described here, the enquiry comes from a connected Meta lead-form source and has Meta’s lead identifier. Open that source from the Meta list in Ad feedback rather than assuming every website enquiry belongs to it. A website visit containing fbclid or a conversation from a click-to-WhatsApp ad is a different input path. Those identifiers alone do not make that enquiry part of this Meta lead-form feedback setup.

For Google website enquiries, check that the actual captured record carries a supported Google click identifier: gclid, gbraid or wbraid. A source called Google, a campaign name or UTM tags alone do not supply that identifier. Follow the visitor’s real form path and confirm what your intake saved. Do not paste invented click identifiers into customer records or treat a successful connection as proof that your website preserves them.

Check capture before outcomes: establish that the source saves the right information, then verify the stage and destination. Test enquiries are excluded from normal outcome sending; the dedicated provider tests have a separate purpose. Investigate capture with a controlled test. Review genuine outcomes in their normal course rather than marking a customer Won to exercise a connection.

In Ad feedback, find the intended Meta source and choose Settings. Open Signals back to Meta, switch on Send signals to Meta and inspect Dataset (pixel). Select the dataset belonging to this advertising setup, checking the associated account where shown. If the list is empty, the Facebook login may lack access. Ask the ads administrator to grant the necessary access, then reconnect; choosing an unrelated visible dataset does not solve that permission problem.

Review A new lead arrives and each Moves to stage row. The defaults describe the funnel with Lead, Contacted, QualifiedLead and ConvertedLead events. Use the event selections deliberately, keeping at least two enabled funnel events across the initial lead, contacting, discussion and won stages. The Lost event does not satisfy that requirement. Read any validation message before saving, and use — don’t tell Meta — only where you intend to leave a stage unmapped.

If Lost has an event, review Tell Meta it was a bad lead only when it’s lost because…. The default selection is Not a fit / out of area and No response. A person who chose a competitor or declined on price can still have been an appropriate prospect. Choose reasons according to your actual qualification policy rather than reporting every unsuccessful sale as a bad lead. Choose Save and confirm the saved settings.

• Configure each Meta lead-ads source separately; another source can use different settings.
• Before enabling, account for the recent enquiries already in this source.
• Enabling plans the initial event and current stage for enquiries received in the last seven days; it is not an automatic upload of the entire archive.

After the Meta settings are saved and enabled, use Test code (optional) if you are checking a provider test session, then choose Send a test event. Kibi sends a dedicated Contacted test event to the selected dataset. The current Kibi prompt points to Events Manager → Test events for the code. Meta’s layout can change, so follow its current test-event instructions and confirm the dataset rather than searching by an old screenshot alone.

Check the test result in Kibi and the corresponding test activity in Meta. Compare the event, destination and time. A processed test establishes a useful delivery check; it does not show that a real lead was attributed to an ad, that a campaign is eligible for a particular optimisation setting or that results will improve. Keep any visible Demo Meta badge in view: simulated activity is not evidence of live provider processing.

For real Meta enquiries, Kibi can plan missing earlier funnel events before a later event. Seeing several entries after a direct move to Won can therefore be expected. Normal events are sent once per enquiry and stage rather than every time someone moves a record back and forth. Won waits briefly for the value to be entered. Read the log’s stage, note and state before treating this expected sequencing as duplicate delivery.

In the Google Ads card, choose Connect Google Ads and complete the provider’s authorised sign-in. On returning, use Which Google Ads account? to select the intended account. Compare both its name and account number with the ads administrator’s record. Accounts marked view only cannot be used for this setup. A connected Google login is the beginning of configuration, not a selected advertising destination and not a connection to Gmail.

Review the conversion actions available for each stage. If you use Create them for me, Kibi creates Kibi · Qualified lead and Kibi · Won in the selected Google Ads account and selects suitable actions. This changes that external account, so confirm the destination before pressing it. If your ads team already maintains appropriate enabled actions, choose those deliberately instead. Keep the action names and stage meanings clear enough for another administrator to recognise.

Choose which of Contacted, Qualified (in discussion), Won and Lost should send an action, using Don’t tell Google for unmapped stages. At least one stage must be mapped to enable feedback. Check the currency warning when the Google Ads account and workspace use different currencies: Kibi omits the Won value rather than converting it. Do not assume that a reported conversion carries the value or currency you expected merely because the action is selected.

Also match by email and phone adds hashed contact identifiers to the Google feedback when enabled. Review Google’s enhanced-conversion requirements with the person who manages the advertising and website setup. Enabling this option in Kibi does not configure every required Google Ads or website setting. Hashing changes the representation of the identifier; it does not make the information anonymous or remove the need to handle it appropriately.

Where Kibi asks for consent confirmation, check the actual wording and collection on the forms first. The checkbox says Our forms ask people for consent to share their data with Google for advertising. Select it only when that statement is true for the data you intend to send. The confirmation is not a form builder and does not add a consent question to a website. Resolve a missing collection process before relying on the setting.

Choose Turn on, or Save when already enabled. If unavailable, check the plan, account, mapped actions and required consent confirmation, then read the inline explanation. Follow Google’s current documentation for provider-side setup; requirements can change. Record who approved the destination and matching settings without copying passwords, tokens or customer lists into notes.

Once feedback is enabled, Send a test conversion performs a validation-only request: Google checks it and records no conversion. This dedicated test currently uses Qualified (in discussion), so that stage needs a selected conversion action. A valid Won-only configuration can therefore report Choose a conversion action first when tested. Review the mapping deliberately; do not change a real customer’s stage to make the test run.

For genuine eligible enquiries reaching a selected stage, inspect What Google heard. The entries identify the conversion action and stage, with Sent, Waiting, Didn’t go or Skipped states and any relevant notes. Compare the enquiry’s captured identifier and real stage with the configured mapping. A successful upload is one part of the measurement chain; use Google’s own diagnostics and reporting to investigate matching, eligibility and attribution separately.

Do not toggle a customer’s stage to produce more rows. Kibi queues normal Google feedback once per enquiry and stage, and Won waits briefly for a value. Check a Waiting entry’s timing and note before considering a retry. Record configuration validation, accepted delivery and provider-attributed conversions as separate results.

If no row appears, confirm the provider is enabled, the enquiry is eligible and its stage is mapped. For Meta, check the specific source, dataset and lead-form identity. For Google, check the workspace configuration and supported captured click identifier. Also check whether the record is marked as a test or its stage already has feedback. These cases require different actions; a missing row does not by itself mean the provider login has expired.

If an entry is pending or Waiting, read its note and allow the scheduled attempt to settle. If it is not sent or Skipped, read the stated reason: an excluded test, an unmapped or intentionally excluded outcome, an old click or an inactive plan is different from a temporary transport failure. If the connection says Needs reconnecting, use the relevant reconnect flow with an authorised account before judging whether later delivery has recovered.

For a failed entry, correct the reported problem before using Meta’s Retry or Google’s Try again. Kibi retries temporary failures, but retries do not grant missing account access or change an invalid destination. Keep the event or action name, time and redacted error if help is needed. Hide customer contact details, lead identifiers and private account values in screenshots. Never send a password, session cookie or provider access token in a support message.

• No expected row: check eligibility and stage mapping first.
• Waiting: check the planned timing, especially for Won.
• Skipped: read the reason before attempting to resend.
• Failed: fix access or configuration, then use the offered retry control.

Record the selected account or dataset, stage mappings and person maintaining them. Review the setup when an agency changes, a login is removed, a form is replaced or qualification changes. To stop new outcomes being queued, disable Meta signals and save, or use Turn off for Google. Already queued signals may still finish; events received by a provider are not undone.

Outcome signals, captured enquiries, advertising spend and recorded sales answer different questions. Imported Meta ad spend · Beta — Available after a short review; Imported Google ad spend · Coming. Their availability is separate from feedback. Compare the measures with the same dates and a clear definition of Won, while keeping provider-attributed conversions distinct from Kibi’s enquiry outcomes. Neither a Sent row nor a rising enquiry count guarantees lower acquisition cost or more revenue. Maintain honest stages and a reliable customer follow-up process alongside the connection.