Search Console and paid media analytics beside product revenue

Acquisition reporting needs three different truths. Search and advertising platforms describe impressions, clicks, cost and provider-attributed conversions. First-party product analytics describes visits, activation, friction and journeys on your properties. A verified payment gateway describes revenue, refunds, churn and recovery. MetricFold places these sources beside one another without silently treating their definitions as interchangeable.

Native acquisition connections support Google Search Console, Bing Webmaster Tools, Google Ads, Meta Ads and LinkedIn Ads. Credentials are encrypted, provider responses are normalized into bounded daily snapshots and each sync has visible freshness and error evidence.

What organic search connections add

The browser referrer can usually tell you that a visit came from Google or Bing, plus the exact referring URL when the browser supplies it. Modern search traffic rarely exposes the organic query in that referrer. Search Console and Bing Webmaster therefore provide a different dataset: query and page performance reported by the search engine.

Google's Search Analytics API can group clicks, impressions, click-through rate and average position by query, page, country, device and date. The official Search Analytics query reference documents that the API returns top rows within internal bounds rather than guaranteeing every row. MetricFold keeps that truncation boundary visible. A missing query is not automatically zero demand.

Search Console properties require OAuth authorization and access to the exact URL-prefix or domain property. The connector cannot manufacture property ownership. Bing Webmaster similarly exposes rank and traffic statistics through its authenticated API.

What paid media connections add

Google Ads, Meta Ads and LinkedIn Ads can provide campaign spend, impressions, clicks and provider conversions. MetricFold stores provider-native values with provider, account, campaign, date and currency dimensions. It does not overwrite verified product revenue with an ad platform conversion value.

Google Ads expresses cost in micros. Convert once into an integer minor or micro-unit contract and retain currency. The Google Ads conversion reporting guide documents conversion metrics and their attribution semantics; it also warns that reporting data is not instant and that zero-metric rows may be omitted. MetricFold records snapshot freshness so a temporary provider lag is not presented as a sudden business collapse.

Provider conversion counts can differ from product payments because of attribution window, view-through credit, cross-device modelling, consent, timezone, conversion-action configuration and data latency. Keep both numbers visible:

Connect a provider safely

Use a read-only credential or OAuth scope where the provider permits it. Select the exact property, account and currency. Test the connection with a bounded date window, then enable scheduled sync. MetricFold encrypts the credential and does not return it to the browser after storage.

The connection workflow should fail closed when an account id is outside the authorized provider response. Rate limits, revoked access, permission changes and provider review are external boundaries. They appear as connection health, not as empty zero-valued business metrics.

Compare campaigns to first-party outcomes

Tag controlled campaign links with source, medium, campaign and content values. MetricFold's free UTM campaign builder preserves the destination URL's existing query and fragment. The first-party tracker captures the bounded campaign fields at entry and discards arbitrary raw query parameters.

Use consistent campaign keys across the ad provider and landing URL so aggregated spend can be compared with first-party visits, activation and verified revenue. Do not require a person-level advertising identifier merely to calculate campaign economics.

At campaign level, useful derived metrics include:

• first-party landing visits per provider click;
• activation rate per campaign;
• checkout-start and verified-payment conversion;
• spend divided by attributed verified payments;
• verified net revenue divided by spend;
• unattributed revenue share;
• source-specific friction and Core Web Vitals;
• lag from first visit to first payment.

These are decision aids, not causal proof. Differences can reveal a landing-page mismatch, broken tagging, poor traffic quality, provider latency or an attribution-window mismatch. Investigate the evidence before changing budget.

Use exact referral and keyword evidence correctly

MetricFold retains normalized referrer host and permitted full referring URL where available. This lets you distinguish a specific partner page, social post or directory URL rather than seeing only a domain. Organic keyword attribution comes from the authorized Search Console or Bing dataset and is aggregated by query/page/date; it is not attached to a named visitor.

For paid search, provider search-term reports may contain sensitive or low-volume values and have their own availability policies. Import only the dimensions needed for campaign decisions, apply bounded row limits and treat absent terms according to the provider documentation.

Build a reliable operating cadence

Sync recent dates repeatedly because providers can revise attribution and late conversions. Use an idempotency key for provider, account, metric, dimensions and date so retries update the same snapshot. Keep the captured-at time and provider event date separate.

Schedule a weekly report that combines spend, impressions, clicks, product visits, activation, verified revenue and data freshness. Add threshold alerts for a material traffic drop, spend without product visits, an activation fall or verified revenue disappearing while provider conversions continue. Alerts should require a minimum volume and cooldown so normal low-volume variance does not create noise.

MetricFold's Growth Operations screen manages acquisition connections, scheduled email or Slack summaries and threshold/spike conditions. Provider credentials and account approval remain customer-supplied external dependencies.

Validate before trusting ROAS

Run a tagged test click from each campaign family, confirm the landing event and semantic CTA, complete a provider test-mode checkout and reconcile the signed webhook. Compare timezone, currency and reporting dates. Replay sync and webhook inputs to confirm idempotency. Revoke a test credential and verify the connection reports failure without deleting prior snapshots.

Only after those checks should a consolidated dashboard show provider spend beside verified revenue. Keep provider-attributed conversions as a separate series and name the attribution model. That clarity makes the dashboard useful for budget decisions and for an AI analyst that must reason from bounded evidence.

Diagnose common acquisition mismatches

Clicks are much higher than first-party visits

Check timezone, date window, campaign redirects, consent and tracker loading before calling the clicks fraudulent. One person may click multiple times, leave before the page runs, use a blocker or land on a broken redirect. Provider invalid-click filtering and MetricFold human-traffic classification answer different questions. Compare landing response status, tagged URL preservation, accepted/excluded traffic and page performance by campaign.

Revenue exists but campaigns look empty

Confirm the attribution token was created before checkout, added to the provider metadata and returned in the signed webhook. Cross-device and delayed purchases may legitimately remain unattributed. Show that share instead of assigning it to direct traffic. The payment integration guide covers provider metadata and webhook reconciliation.

Search impressions move before product traffic

Search impressions, clicks and product visits have different time and aggregation rules. Check property scope, Search Console freshness, country/device filters and canonical page selection. A ranking or impression change may not yield a visit if click-through rate falls. Use the query/page rows to find the affected surface, then compare the corresponding MetricFold entry page rather than the whole site.

Frequently asked questions

Can MetricFold identify the exact organic keyword for each visitor?

Usually no, and it should not invent one. The exact referring URL is stored when the browser supplies a permitted referrer. Organic query evidence comes from the search provider as aggregated query/page/date rows. It can explain which pages receive query demand without claiming that a particular anonymous person used a particular query.

Is provider ROAS the same as verified revenue divided by spend?

No. An ad platform applies its own conversion actions, windows and attribution model. MetricFold's trusted revenue originates in signed gateway events and may use a first-touch or last-touch join. Show provider conversion value and verified attributed net revenue as separately named metrics. Investigate the difference; do not silently substitute one for the other.

Should advertising conversions be sent back from MetricFold?

Only through an explicit destination rule with allowed event types, fields and consent purpose. Core analytics does not automatically activate Google, Meta, LinkedIn or another advertising destination. Delivery should be idempotent, signed where appropriate and visible in an audit log. The revenue attribution guide describes that policy boundary.