How to Get Access to Your Influ2 Data in BigQuery

Last updated: April 20, 2026

Getting your Influ2 data into BigQuery means your analytics team can query Influ2 program performance directly — joining it with CRM data, building custom dashboards, or feeding it into attribution models. Influ2 handles the setup for you, so all you need to do is ask your CSM and plug in the credentials on your end. Here’s how it works.

Before you start

  • You'll need to be in touch with your CSM — they kick off the dataset creation on Influ2's side.

  • Your data or analytics team should be ready to receive Google Cloud service account credentials.

  • Decide in advance whether the default dataset will cover your reporting needs, or whether you'll need custom metrics (more on this below).

What Influ2 takes care of

Your BigQuery dataset lives in Influ2's infrastructure, so there's nothing to configure on the Google Cloud side from your team. Influ2 will:

  • Create a dedicated BigQuery dataset for your account.

  • Set up a service account with read access to that dataset.

  • Share the service account credentials and a link to the dataset with your CSM.

You'll receive everything you need to start querying — no permissions, scopes, or dataset naming work required on your side.

Steps

  1. Reach out to your CSM: Let them know you'd like to enable BigQuery data sync. Mention whether you want the default dataset or have specific metric customizations in mind.

  2. Review the default dataset structure: Influ2 exports raw advertising statistics grouped by:

    1. date

    2. target_id

    3. Cohort_id

    4. stage

    5. content_id

    If you'd like a sample of the exact columns and row format before you commit, your CSM can share one on request.

  3. Decide if you need customization: If the default grouping and metrics cover your reporting, skip ahead.

    1. If you need additional metrics — for example, custom engagement breakdowns or fields tied to a specific attribution model — send your CSM a description of what you need and why.

  4. Receive the service account and dataset link once setup is complete. Your CSM will hand these over directly.

  5. Hand the credentials to your data team to connect BigQuery to your reporting tool of choice (Looker, Tableau, dbt, a notebook, etc.).

What you'll see

Once the service account is active, your team can query the dataset like any other BigQuery source. You'll see tables populated with campaign-level raw statistics, refreshed daily.

  • Sync frequency — the dataset is updated on a daily basis, so your reporting reflects activity from the previous day.

  • Historical data and corrections — data can be updated for the last 7 days. This means if an impression, click, or other event is revised upstream within that window, the correction will flow through to BigQuery. Data older than 7 days is considered final.

  • Data scope — by default, the dataset contains raw statistics (impressions, clicks, and related engagement signals) grouped by date, target, cohort, and content. If you need targets, signals, opportunity/revenue attribution, or other data objects added to the export, that falls under customization — flag it with your CSM.

Customizing the dataset

The default dataset is designed to cover most reporting use cases, but Influ2 supports custom exports when a client needs something specific. Common reasons to customize:

  • You need metrics that aren't in the default grouping (for example, engagement rolled up at the account level using custom parent/child logic).

  • You're building an attribution model that requires joining Influ2 data with specific CRM fields.

  • You need additional columns surfaced in the raw statistics table.

To request customization: send your CSM a clear description of what metrics or fields you need and the report they'll feed into. Influ2's team will scope the work and confirm what's feasible before building the custom export.

Keep in mind

  • There's no self-serve setup — every BigQuery dataset is provisioned by Influ2, so start with your CSM.

  • Credentials are tied to a single service account per client. Store them securely and share only with the team members who need query access.

  • The 7-day update window applies to corrections only. Once data is older than 7 days in BigQuery, treat it as stable for reporting.

What's next

Once your team is pulling data, the most common next step is building dashboards that blend Influ2 performance data with CRM or revenue data. If you're looking for guidance on specific reporting patterns — or if you hit any issues accessing the dataset — reach out to your CSM or contact support.