Skip to main content
These providers enrich Analytics; they do not authenticate Feedback or App Logs.

​
Integration/scoping matrix

​
Stripe prerequisites, validation, webhook creation, and attribution metadata

Stripe supplies revenue data for Analytics. Paste a restricted Stripe API key for the current site. Aiola validates the key and automatically creates the required webhook endpoint; the key must allow Webhook endpoints: Write. To attribute a payment, include these exact Checkout Session metadata keys:
Use Settings → Analytics → Stripe Revenue Tracking → Add to App to update the checkout-session creation path.

​
Google OAuth connection and multiple-account behavior

Google Search Console uses OAuth. Connect another account adds another connection; disconnect acts on the selected account.

​
Bing API-key connection and multiple-account behavior

Bing Webmaster Tools uses an API key. Multiple saved accounts are selectable and independently disconnectable.

​
Per-site property/site mapping

Open Settings → Analytics → Search Keywords and choose the exact Google property and Bing site. gsc_property and bing_site_url are each capped at 500 characters.

​
Disconnect effects

Disconnecting Stripe deletes the site’s stored restricted key and webhook secret and stops revenue webhooks. Disconnecting a Google or Bing account removes that account connection; reconnect before selecting its properties again.

​
Verification and expected data delay

Confirm Stripe shows Connected, then make a test Checkout Session carrying both metadata keys. Confirm Google/Bing selectors list the expected property/site. Search Console data is delayed by about 48 hours. Continue with Set Up Analytics and the Analytics revenue reference.