Skip to content
DatahashDatahashDatahash

Quickstart

This walks through the shortest complete path: one source, one destination, one mapping. The specifics vary by connector, so use the individual source and destination pages for credential details.

Before you start

Section titled “Before you start”
  • Access to a Datahash Studio account, with a project created.
  • Credentials or sign in access for the source system you want to read from.
  • Admin access on the advertising platform you want to send to.

Step 1. Sign in

Section titled “Step 1. Sign in”

  1. Go to https://studio.datahash.com/login.

  2. Sign in with your email and password, or use passwordless sign in with a one time password or Sign in with Google.

  3. Select the project you want to work in.

Step 2. Connect a source

Section titled “Step 2. Connect a source”

  1. Open Sources and find the category that matches your system.

  2. Click the connector tile.

  3. Select the Integration Type if the connector asks for one. This determines which destinations the connection can feed.

  4. Enter the credentials the connector asks for. Depending on the connector this is a sign in, an API key pair, or a credentials file.

  5. Validate. CRM connectors use Test Connection. File and storage connectors use Validate Credentials. Query based connectors offer Preview Results.

  6. Click Next, then Finish.

If you leave before finishing, the connection stays Pending. Select its name in Manage connections to resume.

Step 3. Connect a destination

Section titled “Step 3. Connect a destination”

  1. Open Destination and find the platform you advertise on.

  2. Click the connector tile.

  3. Authenticate. Single sign-on is the recommended route where the connector offers it. Meta destinations also accept manual entry of Dataset ID and Access Token, followed by Validate Credentials.

  4. Give the connection a name, select the target account or dataset, and click Finish.

Step 4. Map your fields

Section titled “Step 4. Map your fields”

On Field Mapping, match each field the destination expects to a column in your source. Studio only shows columns whose data type is eligible for the field, so if a column is missing from the dropdown, its type is the reason.

Map as many identifiers as you hold. Email and phone carry the most matching weight. Sending geography, gender and date of birth alone is not enough, and Meta treats an event carrying only those as invalid.

Fields you cannot unselect

Section titled “Fields you cannot unselect”

On website sources these five are pre-selected because they are necessary to send, and they cannot be unselected.

  • Browser Agent
  • City
  • Country
  • IP
  • Pixel Id

Website sources have a tag to install before any of this matters. See Website tag setup.

Step 5. Verify

Section titled “Step 5. Verify”

Check the events arriving on the platform side rather than in Studio.

  • Meta: Events Manager, Test Events. Use real test data, because Meta may discard events carrying fake personal data that does not match an account. Receipt takes around 20 minutes.
  • Signals Gateway: allow up to 30 minutes for events to appear. If nothing arrives, check the pixel connection and the subdomain setup.

Disable the ad platform’s in-page event setup tool while you test. It interferes with Conversions API events firing.

Where to go next

Section titled “Where to go next”