Vizzybl LogoVizzybl LogoVizzybl

Connections

Connect Google Search Console, Google Analytics 4, Cloudflare, Trello, Workfront, and Discord to enrich your Vizzybl data.

Connections

Connect third-party services to bring external data into Vizzybl. Connections are managed from Settings > Connections.

Google Search Console

Connect your Google Search Console account to import real search query data and use it for prompt monitoring.

Setup

  1. Click Connect Google Search Console
  2. Sign in with your Google account and grant Vizzybl read-only access
  3. Select which properties to enable — Vizzybl lists all properties your Google account has access to
  4. Click Save

What syncs

Once connected, you can:

  • Import search queries as monitoring prompts — see Generating Prompts
  • View query performance data (clicks, impressions, CTR, average position)
  • Filter by date range (last 7, 28, or 90 days)

Property permissions

Vizzybl shows your permission level for each property (Owner, Full, Restricted). You need at least Restricted access to import queries.

Google Analytics 4

Connect your GA4 property to track AI-driven traffic to your website.

Setup

  1. Click Connect Google Analytics
  2. Sign in with your Google account and grant read-only access
  3. Select your GA4 property from the list
  4. Click Save

What syncs

  • AI traffic sessions and users — Visits attributed to AI sources (ChatGPT, Perplexity, Claude, Gemini)
  • Engagement metrics — Bounce rate and session duration compared across traffic sources
  • Conversions — Conversion events attributed to AI-driven traffic

This data powers the AI Traffic tab on the dashboard.

Note: GA4 data is typically 24–48 hours behind real time. A freshness indicator on the dashboard shows when data was last collected.

Cloudflare

Connect Cloudflare to see which AI crawlers are fetching your content — GPTBot, ClaudeBot, PerplexityBot and more — the traffic traditional analytics never show you. This powers the AI Crawlers view on the AI Traffic tab and is available on Pro and above.

There are three ways to connect, from lowest to highest effort. You only need one.

Paste a scoped Cloudflare API token and Vizzybl pulls your AI-crawler traffic once a day. Nothing to deploy.

  1. In Cloudflare, go to My Profile → API Tokens → Create Token → Custom Token
  2. Grant Zone · Analytics · Read (and Account · Analytics · Read) scoped to your zone
  3. Copy your Zone ID and Account ID from the zone Overview page
  4. Paste all three into the Cloudflare card and click Connect

This gives you the headline metrics — which bots, how often, day-over-day trend, and the split between training, search, and live user-fetch crawlers. Per-page detail is not available with this method, because Cloudflare's analytics API groups by bot rather than by page.

Real-time Worker (all Cloudflare plans)

Deploy a tiny, non-blocking Cloudflare Worker that reports AI-crawler hits to Vizzybl in real time. It works on every Cloudflare plan and adds per-page data so you can see exactly which pages AI engines fetch.

  1. In the Cloudflare card, choose Worker and copy the two values shown (an ingest URL and a site token)
  2. Create a Worker in Cloudflare, paste the provided snippet, and add the two values as variables
  3. Add a route so the Worker runs on your site (for example, your domain and all paths beneath it)

The Worker only ever sends request metadata — user agent, method, host, page path, response status, and response size. It never sends query strings, cookies, page content, or visitor IP addresses, and it never slows your visitors down.

Logpush (Cloudflare Enterprise)

On Cloudflare Enterprise you can point a Logpush job at Vizzybl instead of running a Worker. The Cloudflare card gives you the destination URL and the header to add. Keep the batch size small so logs arrive promptly.

What syncs

  • AI crawler hits by bot (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and more)
  • By purpose — training crawlers vs. search and answer bots vs. live user-triggered fetches
  • Daily trend of crawler activity
  • Most-crawled pages — Worker and Logpush methods only

Note: Data appears within about 24 hours of connecting. Vizzybl stores only crawler metadata, never page content or visitor identities.

Trello

Connect Trello to sync your Actions Board with a Trello board — both directions. Available on Pro and above.

Setup

  1. Click Connect Trello and authorize Vizzybl in Trello
  2. Back in the Trello card, pick the board to sync with. Vizzybl adds four lists — Pending, In Progress, Completed, Ignored — if they don't already exist (matching by name if they do)
  3. That's it — a webhook is registered automatically so changes flow both ways

What syncs

  • Send to Trello — Each card on your Actions Board gets a Send to Trello button that creates a matching Trello card in the list for its current status.
  • Both-way status sync — Move a synced card between columns on the Actions Board and it moves lists in Trello; move it between lists in Trello and it updates on the board. Completing it in either tool records the completion once, and counts toward your throughput stats.
  • Attribution — A move you make in Vizzybl is attributed to you. A move made in Trello is attributed to the integration.

Note: Your Trello token is encrypted at rest and never leaves Vizzybl's servers. Disconnecting removes the webhook and stops syncing — existing Trello cards and their links are left in place.

Adobe Workfront

Connect Adobe Workfront to sync your Actions Board with a Workfront project — both directions. Available on Pro and above.

What you need

  • A paid Adobe Workfront plan. The free External access level cannot use the Workfront API.
  • A Workfront system administrator with at least a Standard license to run the setup. This is required both to create the OAuth2 application and for the sync subscription Vizzybl registers — a non-admin will hit an error at the project step.
  • A free OAuth2 application slot. Workfront allows a maximum of 10 per instance.
  • Your Workfront domain, for example yourcompany.my.workfront.com. Preview and Sandbox domains work for testing.

Create the OAuth2 application

  1. In Workfront, go to Setup → System → OAuth2 Applications → Create app integration.
  2. Choose Web Application.
  3. Under Redirect URLs, paste the callback URL shown on the Workfront connection card in Vizzybl (Settings → Connections).
  4. Copy the Client ID and Client Secret. Workfront shows the secret only once — if you lose it, delete the app and create a new one.
  5. In Vizzybl, paste your domain, Client ID, and Client Secret into the Workfront card and click Connect, then approve the authorization screen.
  6. Pick the Workfront project new action cards should land in.

How the sync works

Each card becomes a Task in the project you chose. Board moves update the task status (Pending → New, In Progress → In Progress, Completed → Complete), and completing or updating the task in Workfront moves the card on your board. The Ignored column is not pushed to Workfront. Credentials and tokens are encrypted at rest.

Note: Like the Trello integration, Workfront sync is available on Pro and above.

Discord

Connect Discord to receive notifications and collaborate with your team.

Setup

  1. Click Connect Discord
  2. Follow the Discord authorization flow
  3. Select the channel where Vizzybl should post notifications

What you receive

Discord notifications can include alerts about completed audits, significant visibility changes, and team activity.

Troubleshooting

"Access denied" during Google OAuth

Make sure you are signing in with the Google account that has access to the Search Console property or GA4 property you want to connect. Vizzybl requests read-only access and cannot see properties your Google account doesn't have permission for.

Data not appearing after connection

Google data can take up to 48 hours to fully sync. If data still doesn't appear after 48 hours, try disconnecting and reconnecting the service.

Disconnecting a service

Click Disconnect on any connected service to revoke Vizzybl's access. This stops data syncing immediately. Previously imported data (like prompts created from GSC queries) is not deleted.

Next steps