Skip to main content

How do I map the Unibuddy applicant ID to a unique ID in Slate?

Unibuddy sends a unique ID for each prospect in the applicant_id field. This should be mapped to a unique person field in Slate so that Slate can identify the corresponding prospect record.

Written by Laura Hillman

Complete this step during the Remap stage of your Slate setup, after your sample data has arrived and before activating Remapping.

This mapping is also required if you're setting up Community join interactions.

Step 1 — Create the Unibuddy ID field in Slate

In Slate:

  1. Select Database from the top navigation bar.

  2. Select Fields.

  3. Select Insert and configure the field as follows:

  • Status: Active

  • Scope: Person

  • ID: unibuddy_id

  • Name: Unibuddy ID

  • Prompt: No prompt list

  • Value: Store Value

  • Multiple: Single Value

  • Unique: Value contains a unique ID that identifies a single record for merging

  • Data Type: Text/Unspecified

4. Then save.

Step 2 — Map the Unibuddy applicant ID

Once your sample data has arrived:

  1. Open your Unibuddy Source Format.

  2. Select Remap.

  3. Find applicant_id.

  4. Map it to Destination → Fields → Other → Unibuddy ID.
    ​

  5. Save your mapping.

Note: applicant_id is the field sent by Unibuddy. Unibuddy ID is the Slate field you've created to store that value.

For further information about importing current person data, see Slate's article about it here.

What's next?

Continue with the remaining field mappings in Slate Setup Part 2: Syncing with Unibuddy.
​

If you're setting up Community interactions, you can then follow How do I add Community join interactions to a user record timeline in Slate?

Did this answer your question?