Verified proof import

Switching from another social-proof tool, or launching a campaign that already has a history? Verified proof import lets you bring past activity (sign-ups, registrations, purchases and more) into a RAVE™ campaign so your cards have real people to show from day one.

The key word is verified: RAVE™ only shows imported rows it can confirm, or rows you approve yourself.

Before you start

• Export a CSV from your old tool or database (for example a Proof, FOMO or TrustPulse export). The first row must be column names. Comma- or semicolon-separated files both work, up to 20 MB per file.
• Connect a verification source (recommended). In the workspace sidebar, open Settings and add a key under Verification connections: ActiveCampaign, HighLevel (GoHighLevel), ClickFunnels 2.0 or Stripe. Keys are encrypted and used only for lookups.

Columns RAVE™ understands

RAVE™ guesses which column is which from the header row, and you can change any mapping. If the file has no event type column, you pick one event type for every row. A full name in the first-name column is split automatically when there is no last-name column. Rows with neither a first name nor an email are skipped.

Run an import

1. 1

   Open the campaign's imports

   Open the campaign and click Imports, or use Proof import in the sidebar and click Import proof next to the campaign.

2. 2

   Choose the CSV file

   RAVE™ shows how many rows it found and how many are usable.

3. 3

   Map columns

   Check each field and the "First row" preview.

4. 4

   Pick a source label

   Proof export, FOMO export, TrustPulse export, own database or other.

5. 5

   Pick a verification method

   See the options below.

6. 6

   Confirm the activity is real

   Tick I confirm this activity is real: these people really signed up or bought, and you have the right to show their first name, last initial and city.

7. 7

   Import

   Click Import N rows. When it finishes you see how many rows were verified and how many are waiting for review.

Verification methods

• Source match (ActiveCampaign, HighLevel or ClickFunnels 2.0 contacts): the email must exist as a contact, created no later than one day after the row's date.
• Payment match (Stripe customers and charges): the email must belong to a Stripe customer. Purchase and upsell rows also need a successful charge within two days of the row's date.
• No match: nothing is checked automatically. Every row goes to the review queue.

Rows that fail a check, or have no valid email, are not discarded. They wait in the review queue.

The review queue

The Review queue on the imports page lists rows RAVE™ couldn't verify. They are never shown until you approve them. Tick rows, then click Approve selected or Reject selected.

Managing imports

The Imports list shows each batch with its status (verified, partial, pending or rejected), the verification method and row counts. Remove deletes the batch and all its events in one click.

Imported activity follows the campaign's Lookback setting on the Privacy tab: rows older than the lookback window never show on cards. If you import a year of history but the lookback is 30 days, only the last 30 days appear.

Importing from your own server

For large or recurring imports, your server can send rows to the RAVE™ API (POST /api/v1/imports), signed with the workspace's secret from Settings → Signed uploads. RAVE™ spot-checks a sample of about 10% of the rows against a connected account, and at least 90% must pass for the rows to show. See the API reference linked from the workspace's API keys section.

The secret is shown masked, with only its last 4 characters. Workspace owners and admins (and account owners and admins) can click Reveal to see and copy it; each reveal is recorded in the audit log. Everyone else sees the masked value only. Rotate secret makes a new one, and uploads signed with the old secret are rejected.

Privacy

Emails are used only for verification and stored as a one-way hash. Full last names are never stored, only the initial. See Privacy and data deletion.

Troubleshooting

• "No rows found": the first row must be column names, followed by at least one data row.
• Everything went to review: check that the email column is mapped and that the right connection is set up in Settings.
• Imported people don't appear: check the campaign's Lookback window and the card's Event types.