Data Sanity and Campaign Governance Guidelines

This page outlines best practices and guidelines to ensure data sanity during ingestion and proper campaign governance in HCL CDP. Following these guidelines helps avoid data redundancy, maintain data quality, and improve campaign performance.

Impact of Compromised Data Sanity

On CDP Profiles

Incorrect Merging of Profiles: Duplicate user identifiers can lead to merging multiple profiles into one, causing data inaccuracies (e.g., wrong email IDs or phone numbers).
Blacklisting: Merging errors may result in blacklisted profiles that cannot be stored in CDP and are only retained in event logs.

On Active Use Cases

Reduced Audience Size: Mismerging reduces segment sizes, leading to fewer impressions for active use cases.
Personalization Errors: Misplaced user data impacts personalized communication, such as macros for names or offers.
Misaligned Targeting: Segments may include users who should not be targeted.

On Reporting

Skewed Metrics: Reduced audience sizes affect campaign performance reports.
Poor Model Accuracy: AI models like lead scoring are impacted due to low-quality data.

Client Guidelines to Ensure Data Sanity

Offline File Ingestion

Formatting Standards:
- Phone Numbers: Use E.164 format (e.g., +918xxxxxxxxx).
- Email IDs: Use lowercase letters only.
- File Format: Must be .tsv (tab-separated values).
- Encoding: Files must be UTF-8 encoded.
File Structure:
- Maintain a consistent order of fields between file versions.
- User identifier columns are case-sensitive and must remain consistent across files.
- Ensure the first column is non-blank.
- Enclose blank last columns in double quotes.
- Escape double quotes within a value using a backslash (\").
Additional Notes:
- Files must be uploaded via an SFTP server.
- Amounts should be numeric and separated into distinct properties for currency and value.

Examples:

Right Format:
```
"price": 3500,
"currency": "INR"
```
Wrong Format:
```
"price": "3500 INR"
```

Website/App Integration

Tracking Plan:

HCL provides a tracking document with event details based on use cases.
Clients must review and inform HCL of changes.

Data Standards:

Email IDs: Use lowercase letters.
Phone Numbers: Follow E.164 format.
Date of Birth: Use YYYY-MM-DD format.

Implementation:

Install the required SDKs (JavaScript, iOS, Android, Flutter, React Native).
Ensure events flow into CDP as per the tracking plan.

Verification:

HCL verifies event flow and flags discrepancies within two working days.

REST API Integration

Integration Guidelines:

Use application/json for content-type headers.
Authenticate using the provided API key.
REST API supports only Identify and Track event types.
Each request has a maximum payload size of 500 KB.

Error Handling:

Exceeding limits returns a 400 Bad Request response.
Response content type is application/json.

Impact of Compromised Campaign Governance

On Customer Experience

Incorrect Targeting: Poor governance leads to wrong users being targeted with incorrect offers.
Hyper-Personalization Failures: Errors in segmentation criteria impact industries like BFSI, Telco, and Retail.

On-Use Case Performance

Segment Issues: Ineffective segmentation reduces the audience size.
Delayed Issue Identification: Problems become apparent only after analyzing poor campaign performance.

Client Guidelines for Campaign Governance

Maker Checker Process

Maker: Client-side business user or HCL Delivery POC.
Checker: HCL Delivery POC (mandatory).
Process: Final activation of use cases must be approved and verified by the Delivery POC.

Use Case Sign-off Conditions

Maintain a detailed email thread with:

Segment and Engagement IDs.
Trigger conditions.
Approval from the Delivery POC.

TATs for Review and Sign-off

Up to 5 Engagements: 1 working day.
6 to 15 Engagements: 2 working days.
More than 15: Timelines discussed via email.

Additional Requests:

Debugging segments or publishing new data points may require extended timelines.