Import your DataFast history into Sumly

Switching from DataFast? Paste its API key and Sumly reads your visitors per day with their pages, referrers, campaigns, countries and devices, for the time before its own script.

Drawn with example numbers.

Moved in three steps

One key, read once. Sumly's own numbers win from the first day it counted.

  1. 1

    In DataFast, open the website's settings and copy its API key, the one that starts with df_. An account token (dft_) works too, with the website's id.

  2. 2

    In Sumly, open Projects and payments › Import earlier history, pick the project and choose DataFast. Paste the key; Sumly checks it at once.

  3. 3

    The import runs in the background and the page follows it. Visitors shows those days, marked as imported from DataFast, once it is done.

What you see once it is in

DataFast next to every other project and provider, on the same pages.

Visitors

The line and the numbers reach back before the script, with a note saying which days came from DataFast.

The lists of pages, sources, campaigns, countries and devices add those days.

Events and Goals

DataFast's goals count under their own names; a goal kept in Sumly for the same event adds them.

Overview

Revenue per 1,000 visitors and conversion for those months.

Counts toward your plan

Nothing: imported visits never count toward your plan. Plans →

What you don't get

No revenue attribution for imported days, and no import of DataFast notes, funnels or goal properties.

The details

What is read
  • Visitors, page views and visits per day, with the bounce rate and the average visit length
  • Each day's goals, with how many people reached each and how often
  • Each day's pages, referrers, campaigns (utm tags), countries, regions, cities, devices, browsers and systems, by visitors
  • Up to 25 months back, as long as Sumly keeps visits
How it is read
  • Through DataFast's API, with the key you give. DataFast gives its lists for a whole range, so Sumly asks for each day with visitors on its own; a long history takes a while.
  • Only the days before Sumly's own script, and never a day Sumly already has, so nothing counts twice.
  • The key is kept encrypted while the import runs and deleted when it is done.
Good to know
  • DataFast gives visitors for each list, not page views, so imported pages show visitors only.
  • No single visits or people: DataFast's API gives totals per day and list. Journeys, funnels and filters start with Sumly's own script.
  • Revenue is not imported. Payments come from your payment provider, up to three years back, and are traced to visits from the script on.

DataFast questions

Do I have to stop DataFast first?

No. Run both while you compare. The import only fills the time before Sumly's script, so the days both counted are Sumly's.

Can I undo the import?

Yes. Import history lists each import with Remove, which takes out what it brought and leaves Sumly's own numbers alone.

Why does it take a while?

DataFast's API answers each list for a range, without days in it. To keep the days, Sumly asks for each day with visitors on its own and waits when DataFast asks it to slow down.

Other integrations

Try it with your own projects

Sign in with Google or a code by e-mail and connect your first project. The first 14 days of a paid plan are free, with no card.

Start free trial

Or look around first: open the live demo.

Pages, integrations, guides and answers