Overview

The SmartMatch import template allows you to connect to TargetSmart’s Smartmatch API by providing a contact list to match on. The import matches on the provided set of contacts and returns the enriched list as a platform table. The script can be configured to automatically match to table columns with supported field identifiers and also optionally configured to include more request parameters. The INCLUDE (email, landline, etc) parameters will add additional information, but also potentially incur additional costs for these attributes.

In order to use the SmartMatch import, you will need:

• A SmartMatch API key.
• A table containing the list of contacts to be matched on

Getting started

Parameters

• SMART MATCH API KEY: TargetSmart provisioned client API key.
• INPUT DATABASE: Name of database to get the contact list to match from.
• INPUT SCHEMA AND TABLE NAME: Name of schema and table where the contact list to match are.
• PO NUMBER: Purchase order number, a user created number for tracking purposes
• AUTO MATCH TABLE COLUMNS TO SMART MATCH FIELDS: If yes, the script will automatically attempt to match your column names to it’s relative smart match supported field.

NOTE: This is not foolproof. Only use this functionality if your table column names are identical to their relative fields supported on Targetsmart. Provide your column names directly if you are unsure.

For example, voterbase_id and voter_id are one of the supported fields in Targetsmart. Your table column names for these fields should have these names in them in order for this to be successful. Your table column name could read my_col_voterbase_id, my_col_voter_id.

• STREAM AND UPLOAD DATA IN BATCHES IN THE CASE OF MILLIONS OF DATASET: If selected, records will be uploaded in batches, otherwise, it uploads all the records at once.

NOTE:

• Unless you are uploading large records, this should be left unchecked as Targetsmart does not play nice with multiple files being uploaded at a time.
• If it is selected and a 403 error is gotten while running the script, reach out to the data-integrations team.
• If a memory limit is encountered, and selecting this option also fails, trying splitting the number of records to upload.

• VOTERBASE ID: The name of the voterbase_id column in your table.
• FULL NAME: The name of the full_name column in your table.
• FIRST NAME: The name of the first_name column in your table
• MIDDLE NAME: The name of the middle_name column in your table.
• LAST NAME: The name of the last_name column in your table.
• ADDRESS 1: The name of the first address line column in your table.
• ADDRESS 2: The name of the second address line column in your table.
• CITY: The name of the city column in your table.
• STATE: The name of the state column in your table.
• ZIP: The name of the zip column in your table.
• PHONE: The name of the phone column in your table.
• EMAIL: The name of the zip column in your table.
• GENDER: The name of the gender column in your table.
• VOTER ID: The name of the voter_id column in your table.
• LATITUDE: The name of the latitude column in your table.
• LONGITUDE: The name of the longitude column in your table.
• DOB: The name of the dob column in your table.
• AGE: The name of the age column in your table.
• SMARTVAN ID: The name of the smartvan_id column in your table.
• EXACT TRACK: The name of the exact_track column in your table.
• FIRST NAME COMBINED: The name of the first_name_combined column in your table.
• NAME SUFFIX: The name of the name_suffix column in your table.
• MATCHBACK ID: The name of the matchback_id column in your table.

NOTE: One or more of the parameters from VOTEBASE ID up to LONGITUDE should be specified. Matching will be done based on the field identifiers found.

• INCLUDE EMAIL, INCLUDE LANDLINE, INCLUDE WIRELESS, INCLUDE VOIP

These parameters allow you to control if the associated phone and email values should be included in your deliverable. TargetSmart may include these data points in your configuration at an extra cost.

NOTE: Setting these values indicates that you desire to receive and potentially incur additional cost for these attributes

• OUTPUT DATABASE: Name of database to write the matched result to.
• OUTPUT SCHEMA AND TABLE NAME: Name of schema and table to write the matched result to.
• ACTION IF TABLE EXISTS(optional): The behavior if a table with the requested name already exists.  If the table does not exist, it will be created for you. Options are:

• Fail: The sync job fails if the table exists
• Append: Records will be appended to the existing table
• Truncate: Records on the table will be wiped out while maintaining the current columns.
• Drop: Removes the entire table including column information.