Looker Reporting

Reporting can be set up and sent via Looker. The examples below showcase metrics at lead-level for more granular look at funnel metrics, and in the aggregate by date for a high-lever look at performance over regular intervals.

Please contact your Partner Manager for more details and to set up reporting via Looker in your desired delivery method.

Delivery Methods

Looker reports can be scheduled on a regular cadence, such as daily or weekly. The most common delivery methods are: email and SFTP. Looker also supports webhook and S3 delivery.

Engine only supports Username/Password authentication at this time.

What Engine Needs

To configure scheduled delivery, please provide:

• Report type: lead-level report, aggregated report, or both

• Delivery method: email, SFTP, webhook, or S3

  • Additional requirements are defined below

• Cadence: daily, weekly, monthly, or another required schedule

• Desired send time: include timezone

• Output format: usually CSV

• Any required filters: for example product, campaign, placement, or client tag

• Business contact: who should receive and validate the report

• Technical contact: who can troubleshoot destination or access issues

If you need your own identifiers in the report output, make sure you are sending Client Tags with your leads. See Appending Client Tags for Reporting & Attribution.

Email

Email is the fastest option to set up. It is best for business users who want a recurring report without engineering work. Please provide:

• Recipient email address list

• Preferred cadence and timezone

• Any required subject line or naming convention, if applicable

SFTP

SFTP is usually the best option if your team wants to ingest flat files into an internal reporting pipeline. Please provide:

• SFTP host

• Port, if not standard

• Username and password

• Destination folder or file path

• Any file naming convention you want used

• Any network restrictions we should know about

Webhook delivery

Webhook delivery is useful when your team wants to trigger an automated workflow when a report is generated. Please provide:

• Destination URL

• Required request method, if your endpoint expects one

• Any required authentication or headers

• Expected success response for delivery testing

• Any required query parameters or path parameters

S3

S3 is a good fit when your team already centralizes reporting files in AWS for downstream processing. Please provide:

• Bucket name

• Target folder or prefix

• Region, if relevant to your setup

• Access instructions or credentials required for delivery

• Any file naming convention you want used

Additional Considerations

To speed up setup, also include:

• Whether you need a test delivery before go-live

• Whether you need historical backfill, or only ongoing scheduled delivery

• The exact client tags or dimensions you expect to see in the report

• A sample destination configuration that will succeed in your environment

The more exact your destination and naming requirements are, the faster reporting can go live.

Standard Reports Available

Here are two reports you can request to see.

Lead-level Metrics

The following is a snapshot of lead-level metrics. This will show you how far leads are progressing in the funnel, and monetization/payout to you, when applicable.

Aggregated Metrics by Date

The following is a snapshot of aggregate performance metrics over certain periods of time. These will give you an idea of how your campaign/placement is peforming overall. This is typically provided ad hoc on request, so your partner manager can review and explain funnel metrics together, and provide guidance when appropriate.

Sample aggregated Looker report