data-matching

Match external tables to ICP flags in Databricks using email, race ID, or position ID join paths.

3|1|Updated Feb 7, 2025

Search Tags:#data transformation #Databricks #data matching #ICP flags #join paths

Ready to run

npx skills add https://github.com/thegoodparty/gp-data-platform --skill data-matching

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-matching
Source: https://github.com/thegoodparty/gp-data-platform/tree/main/.claude/skills/data-matching
Command: npx skills add https://github.com/thegoodparty/gp-data-platform --skill data-matching

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of matching external or ad-hoc tables to ICP flags or other reference data in Databricks, facilitating the attachment of additional information to tables containing people or races.

Core Features & Use Cases

Data Matching: Match external or ad-hoc tables to ICP flags in Databricks using established join paths.
Routing by ID: Routes data based on the type of ID available in the source table (email, race ID, or position ID).
Join Paths: Offers three join paths to match data: via email, via BallotReady race ID, or via direct position ID.
Use Case: For instance, matching a lead list's emails to ICP flags for targeted marketing efforts.

Quick Start

Match a table with emails to ICP flags in Databricks using the 'data-matching' skill.

Frequently Asked Questions about data-matching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I match external data to ICP flags in Databricks?▼

To match external data to ICP flags in Databricks, you route source table records through established join paths based on available identifiers like email, race ID, or position ID. This attaches reference ICP flag data to your ad-hoc tables.

What join paths are available for data matching when I only have an email address?▼

When only an email address is available, data matching uses the campaign join path to route records. This connects your external email lists to the corresponding ICP flags within the Databricks environment.

Can I use position ID or race ID to join ad-hoc tables in Databricks?▼

Yes, you can join ad-hoc tables using direct position ID joins or route data via BallotReady race ID through race staging. These paths match external records to ICP flags when those specific IDs are present.

Do I need prior knowledge of data joins to use this Databricks data matching process?▼

Yes, performing data matching requires knowledge of data joins and a configured Databricks environment. You must identify available IDs in your source table to select the correct join path for ICP flag attachment.

What is the best way to attach ICP flags to a lead list for targeted marketing?▼

The best way to attach ICP flags to a lead list is by matching the source emails to ICP flags using established Databricks join paths. This routes your lead data through campaigns to append the necessary reference flags.

Why does data matching fail when my source table lacks email, race ID, or position ID?▼

Data matching fails without email, race ID, or position ID because the Skill relies on these specific identifiers to route records through established join paths. You must ensure your source table contains at least one supported ID.