weeveo
  • Features
  • How it works
  • Revenue
  • Agents
  • Pricing
  • Docs
Sign in
Start free
weeveoanalytics

Understand your traffic.See what leads to sales.

See where visitors come from, what they do and which visits lead to purchases. Basic statistics without a popup. Recordings require permission.

Start freeService status

© 2026 Weeveo. All rights reserved.

Product

  • Features
  • Revenue reporting
  • Realtime
  • Funnels & journeys
  • Pricing

Developers

  • Documentation
  • Agents & MCP
  • Browser SDK
  • REST API
  • Start free
  • Sign in

Company

  • Changelog
  • Support
  • Contact
  • Privacy policy
  • Terms of service
  • Refund policy
  • Status

weeveo

Skip to content
Documentation home
Start here
Meet WeeveoYour first siteFind your way aroundCore concepts & metrics
Install & track
Install the trackerFramework & CMS recipesTracker configurationBrowser SDK referenceConsent & your CMPVisitor identity & payment matchingVerify your installationCustom tracking domains
Understand your traffic
Overview & realtimeDates, filters & comparisonsSources & campaignsPages & engagementEvents & visitor timelinesExplore, paths & saved viewsTraffic quality & anomalies
Conversions & revenue
Goals & conversionsFunnels & bottlenecksRetention cohortsRevenue reportingConnect a payment providerAttribution modelsCustomer journeysAll payment providers
Experience & performance
Session replaysClick & scroll heatmapsWeb Vitals & performance
Developers & agents
Connect ChatGPT, Claude & agentsCreate & manage API keysREST API quickstartAnalytics query referenceErrors, limits & safe retriesJavaScript & Python examplesMCP transport & tool discoveryOAuth discovery & authorizationPermissions & write consentAsk Weeveo & saved chatsApp identity & plugin metadataHTTP surface referenceAll API & MCP tools
Workspace & privacy
Workspaces & multiple sitesTeam, roles & invitationsSite preferences & notificationsPublic reports, embeds & badgesAccount & securityPrivacy & collection controlsVisitor export & erasure
Operate Weeveo
Background jobs & maintenanceTroubleshooting & common questionsQuestions & analysis recipes
Building something?Explore every API tool Download JSON reference ↗
DocsConversions & revenue
Conversions & revenue

Connect a payment provider

A step-by-step setup for verified payment ingestion.

On this page
1. Choose your provider2. Supply credentials securely3. Configure the webhook4. Verify a payment5. Import history when supported6. Disconnect or rotateTroubleshooting

1. Choose your provider#

Open Integrations for the correct site. Find the provider in the complete directory. Connection forms specify that provider's required fields; not every provider uses the same API key or webhook mechanism.

2. Supply credentials securely#

Create the necessary credential in your provider account and enter it in Weeveo's connection dialog. Keep provider credentials server-side. Weeveo stores integration secrets encrypted; they are inputs, not values returned by list_integrations. Do not put them in the browser tracker or public docs.

3. Configure the webhook#

Copy the exact webhook URL shown by Weeveo. If automatic registration is supported, use that action. Otherwise configure it in the provider dashboard with the required event selection and signing secret. Providers with unsigned notification pointers are verified by fetching the payment from the provider API instead.

4. Verify a payment#

Use the provider's supported test workflow, then inspect webhook status and Revenue. Match live/test modes and credentials. A successful connection test proves the supplied credential works; it does not prove that your provider has delivered a new payment event.

5. Import history when supported#

Use Sync only for providers that advertise history synchronization. The API exposes a bounded import limit. Review sync errors and date coverage before comparing imported revenue with all-time provider totals.

6. Disconnect or rotate#

Disconnect from the selected site when no longer needed. Rotate compromised provider credentials at the provider too. Disconnecting stops the configured connection; it is not a request to erase all previously ingested analytics.

Troubleshooting#

Check webhook delivery logs, the exact canonical HTTPS callback URL, signature secret, account environment, selected site and event status. Reconciliation jobs must run for delayed/self-healing processing. list_webhook_events returns sanitized audit status without raw payment payloads.

Still looking for an answer? Try troubleshooting or get in touch.

PreviousRevenue reportingNextAttribution models
ON THIS PAGE
1. Choose your provider2. Supply credentials securely3. Configure the webhook4. Verify a payment5. Import history when supported6. Disconnect or rotateTroubleshooting
Your sites. Your permission.

Start with read access. Grant changes when you need them.

Understand access

Search Weeveo documentation

Good places to start

Start hereYour first siteGo from a new workspace to your first verified visit.Install & trackInstall the trackerOne shared script, configured for your site and consent policy.Install & trackBrowser SDK referenceTrack actions, inspect consent and identify a permitted persistent visitor.Developers & agentsConnect ChatGPT, Claude & agentsUse OAuth sign-in for hosted agents, with optional API keys for other clients.Developers & agentsAnalytics query referenceExact shared date, traffic, comparison and filter parameters.Developers & agentsAll API & MCP toolsEvery tool, argument schema and permission in the shared registry.
K to open↑ ↓ to select · Enter to open · Esc to close