How to Get Access to Your Influ2 Data in Snowflake

Getting your Influ2 data into Snowflake means your analytics team can query program performance directly in your own warehouse — joining it with CRM data, building custom dashboards, or feeding it into attribution models. Influ2 shares the data through Snowflake's native data sharing, so there are no pipelines to build or files to move: the data appears in your Snowflake account as a read-only database, ready to query. Here's how it works.

Before you start

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

• You'll need an active Snowflake account, and someone on your team with a role that allows accepting inbound data shares — ACCOUNTADMIN, or any role granted the global IMPORT SHARE privilege.

• Region and cloud provider matter. Snowflake supports data sharing only within the same region and cloud provider. Influ2's Snowflake runs on Google Cloud Platform in us-east4 (N. Virginia). If your Snowflake account is in a different region or on a different cloud provider, cross-region or cross-cloud sharing is still possible — reach out to your CSM to set it up.

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

What Influ2 takes care of

The share is provisioned entirely on Influ2's side, so there's nothing to build from your team. Influ2 will:

• Prepare a dedicated dataset for your account.

• Create a secure data share targeted at your Snowflake account.

• Confirm through your CSM once the share is live and ready to accept.

Because the data is shared rather than copied, you're always querying the current dataset — no sync jobs to maintain, and no storage costs for the shared data on your side.

Steps

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

2. Share your Snowflake account details. Your CSM will ask for your Snowflake account identifier (organization name and account name) and confirm your region and cloud provider. You can get both values by running SELECT CURRENT_ORGANIZATION_NAME(), CURRENT_ACCOUNT_NAME(); in your account.

3. 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.

4. Decide if you need customization. If the default grouping and metrics cover your reporting, skip ahead. 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.

5. Accept the share in your Snowflake account. Once your CSM confirms the share is live, your Snowflake admin will see the inbound Influ2 share in Snowsight's data sharing section and can create a database from it.

6. Hand access to your data team. By default, only the role that created the database from the share can query it. Shared databases use a special grant — regular per-table grants don't apply — so grant access with GRANT IMPORTED PRIVILEGES ON DATABASE influ2 TO ROLE <role>; (using whatever database name you chose when accepting the share) for each role that needs it, then connect it to your reporting tool of choice (Looker, Tableau, dbt, a notebook, etc.).

What you'll see

Once the share is accepted, the Influ2 dataset appears in your account as a read-only database your team can query like any other Snowflake source. You'll see tables populated with campaign-level raw statistics.

• Data freshness — Influ2 loads new data daily; once loaded, it's immediately visible in your account, so your reporting reflects activity from the previous day.

• Historical data and corrections — data can be updated for the last 7 days. If an impression, click, or other event is revised upstream within that window, the correction flows through automatically. Data older than 7 days is considered final — treat it as stable for reporting.

• 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, that falls under customization — flag it with your CSM.

• Read-only access — because the data comes through a share, the tables can't be modified on your side. If you need to transform the data, build views or downstream tables in your own databases on top of the shared source.

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.

Keep in mind

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

• Data sharing works within the same region and cloud provider by default. Influ2's Snowflake runs on GCP us-east4 (N. Virginia) — if your account is elsewhere, mention it to your CSM early so cross-region sharing can be arranged.

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