Amazon S3 integration

Deliver Dashworx’s modelled data as files into an Amazon S3 bucket you control, ready for Athena, Glue, data lake pipelines or long-term archiving.

About the Amazon S3 integration

Amazon S3 is AWS’s object storage service and the foundation of many data lakes. Files land in buckets under date-based prefixes, access is controlled with IAM and bucket policies, and services such as Athena, Glue, EMR and SageMaker read straight from them. For data teams, S3 is often the agreed hand-off point: anything that arrives there in a predictable format can be picked up by existing pipelines.

Sending Dashworx data to S3 uses that hand-off. Instead of building collectors for each ad platform and shop back end, the data team receives modelled marketing and eCommerce tables as files, with consistent column names, one channel taxonomy and aligned currencies. Those files can be queried in place with Athena, loaded into a warehouse, or kept as a historical archive under your own retention rules.

It is a flexible option for organisations that prefer to own the storage layer. The marketing team keeps working in Dashworx dashboards and alerts, while the data team decides what happens to the files downstream.

What Dashworx sends to Amazon S3

Daily channel performance files

Campaign spend and revenue

Impressions, clicks and spend

Blended ROAS and CPA

Orders and revenue by day

Product revenue by SKU

Conversions by platform

KPI actuals vs targets

Channel taxonomy mapping

Brand and region dimensions

Sessions by source and medium

…and more.

Send Dashworx data to Amazon S3

Dashworx sends Amazon S3 files containing modelled marketing and eCommerce tables: daily performance by channel, campaign, market and product, with spend, revenue, orders, conversions, ROAS and CPA, plus dimension files for channel, brand and region. KPI targets and actuals can be included as a separate table.

S3 is useful when your data team wants ownership of the storage layer. Files in your own bucket can be governed by your IAM policies, encryption settings and lifecycle rules, queried with Athena, catalogued with Glue or loaded into whichever warehouse you use. Dashworx does the collection and modelling; your pipelines decide what happens next, and nothing about your existing AWS set-up has to change.

How to connect Amazon S3 to Dashworx

01

Choose what to send

Tell us which Dashworx reports, metrics and dimensions should go to Amazon S3, and how often.

02

Authorise access in one click

Sign in to Amazon S3 and give Dashworx permission to deliver data. No API keys or developer time required.

03

We map and schedule your data

The Dashworx team maps your analysis-ready data to Amazon S3’s format and sets up the delivery schedule.

04

Get notified when data is flowing

You’ll receive an in-platform notification once the first delivery lands in Amazon S3.

Frequently asked questions

What does Dashworx do with my connected data?

How long does it take for my data to appear after connecting?

Do I need technical skills or a developer to connect a source?

How often is my data refreshed?

How is my data kept secure?

Can I connect multiple accounts from the same platform?

What if the platform I use isn’t listed?

Connect Amazon S3 in minutes

Book a demo and we’ll show you your own data, connected and visualised, before you commit.