Retargeting readiness
Ask Erdo to audit retargeting. The daily Retargeting monitor is installed for organizations connected to Google Ads, Meta Ads or LinkedIn Ads. It inspects connected platforms independently, so a missing integration or provider capability does not hide findings from the other platforms. Existing organizations receive the monitor through the regular platform monitor sync. Find it in Automations; an intentionally paused monitor stays paused. Existing Google Ads Audiences defaults become Retargeting in place on the next regular refresh; their history and intentionally paused state are retained. For Google Ads, the audit checks the owned page artifact’s configuredAW-... conversion destination. It uses the page-tracking read for meta_pixel
and its enabled state. It also reads a LinkedIn Insight destination when the
tracking read exposes one; otherwise it retains that capability gap and inspects
the owned artifact or a discovered provider read for tag evidence. The page-tracking read’s
google_analytics destination is GA4, not the Google Ads tag. A first-party page
event is not proof that an advertising provider received it; missing or
unsupported evidence remains a capability gap.
What the audit establishes
Segments are evaluated separately: all visitors, engaged visitors, visitors who
opened or started a form without becoming a lead, and converted leads. Erdo only
claims a provider can collect a segment when its tag actually receives the needed
event. Converted leads are excluded from visitor audiences where the provider,
consent and supported integration action allow it.
Missing evidence is shown as unknown, rather than zero or “retargeting off.”
Serving requirements depend on provider, network and audience type. See Google
data segment guidance,
Meta audience guidance,
and LinkedIn website audience guidance.
From a gap to a verified repair
When the monitor finds missing setup, it hands the evidence to an execution agent. The agent reuses existing audiences, work and pending approvals, then proposes the specific changes through approvals. It checks the provider again after execution. The result distinguishes a proposal, a pending approval, an executed change and verified setup. Findings are deduplicated by organization, platform and visitor segment; a declined proposal is not repeated for 30 days. The monitor preserves existing campaign budgets and targeting during repairs. New spend is only proposed for an eligible segment with no target, using the bounded launch proposal below. Any proposed creative must pass the existing ad critic before provider submission. Housing rules still apply. The monitor checks the capabilities returned by action discovery on each run. When an account has no applicable audience or campaign actions, it records the exact missing operation and continues the other platform checks. A past missing LinkedIn capability does not predict what a later integration exposes.When a segment has no campaign
After the provider inventory is complete, if an eligible visitor segment has no campaign targeting it, Erdo can propose one small campaign and its required audience ad group/ad set. This also applies when there are no existing owned campaigns, once Erdo verifies the connected account is dedicated to your organization and the page is live and owned. Use the existing organization/workstream daily amount when specified. If a complete budget-policy read confirms no amount is set, the default is 5 units per day in the account’s currency for seven days, with planned spend of 35 units. Google daily budgets may overdeliver, so the card states the provider’s actual budget behavior; the plan is not presented as a hard cap. Meta uses a lifetime budget equal to the planned seven-day total and seven-day stop time when the connected actions support them (35 units with the default). Any lower organization or workstream budget ceiling applies. A failed or incomplete policy read, known exhausted ceiling, or policy-required strict cap the provider action cannot enforce blocks the proposal; a complete read showing no policy permits the conservative default. The first approval authorizes creation of the proposed campaign in a paused state; it does not authorize serving or spend. A separate approval is required to activate it. The approval request states the currency, dates, planned total and budget behavior. The creative is reviewed with the existing ad critic before submission. Housing restrictions apply to targeting, destination and copy. The monitor uses one continuing finding per organization, platform and segment, reuses pending approvals, and waits 30 days after a declined decision before proposing it again. Existing campaign repair findings remain separate. The monitor discovers the workstreams it can read, follows their declared campaign references and checks the current decisions before proposing a repair. A limited inventory remains a scope gap; campaign names and missing Knowledge records do not establish ownership.Lead exclusions and Customer Match
Before proposing an exclusion, Erdo checks the list’s actual membership rules, its conversion actions and whether the lead event follows a successful saved contact. A list called “All Converters” is not enough: its membership may cover other actions. When that definition cannot be verified, Erdo investigates the measurement gap and leaves the exclusion unchanged. First-party leads from your saved lead dataset can be used for an exclusion list only when their identity and consent cover that use, and the connected provider exposes an approved exclusion action. Erdo never uses purchased or enriched contacts, and does not use lead contacts for prospecting or lookalike expansion. Only provider-normalized SHA-256 email or phone hashes may be sent; raw contacts do not appear in findings. Website audience actions do not imply customer-list support. Erdo discovers Google Customer Match, Meta Custom Audiences and LinkedIn Matched Audiences capabilities on each run. If a provider lacks a compatible upload or exclusion action, Erdo states the missing capability and does not upload. Where an existing row-action declaration supports arrival refresh, Erdo updates that declaration in place and reads it back. The daily monitor checks for eligible leads since the last successful refresh and uses a discovered, approved provider action only if one supports the exclusion upload. If neither path is available, it reports automatic refresh as unavailable with the exact missing capability. Google Customer Match recommendations are separate from website retargeting. This audit does not upload contact data, accept customer-data terms, apply a recommendation or authorize spend. See Google’s Customer Match guide.API access
For connected Google Ads customers, the current read-only readiness action isget_google_ads_audience_readiness(customer_id) or:
list_meta_custom_audiences read
with the ad_account_id returned by list_meta_ad_accounts. It reads only an ad
account your Meta connection was set up to use and refuses any other account the
login can reach. The read is paginated:
Erdo accumulates every page, passing next_cursor as after until has_more is
false, and requires page_status: complete on each response. The action reports
inventory_status: partial for continuation pages, even the last one, so the
accumulated pages plus the final has_more: false establish completion. A failed
page or a missing cursor while more pages exist leaves inventory incomplete.
Meta’s raw delivery_status, operation_status and approximate count bounds are
preserved; eligibility remains unknown until supported campaign-specific
evidence is available. Each audience also carries meta_delivery (ready,
too_small, unusable or unknown). A too_small audience will not deliver yet,
and its count bounds are Meta’s lowest bucket, so it has fewer people than they
show. See Meta Ads. Missing actions are reported as capability gaps, and later
action discovery can clear them. Access remains scoped to the connected
organization and its owned campaigns.
