Tencent Marketing DataNexus SDK Integration Assistant

Problem

Integrating Tencent Marketing DataNexus SDK across mini programs, mini games, APP-iOS, APP-Android, and HarmonyOS often stalls on SDK selection, missing required events, incorrect action_param fields, and mismatched post-integration data. Required event sets differ sharply by surface and business mode, so IAA mini games, IAP/hybrid mini games, mini-program verticals, and game/non-game apps cannot all be handled with one tracking checklist.

Workflow

The skill follows a confirm-surface-first path:

• SDK selection: choose the right SDK for mini programs, mini games, APP-iOS, APP-Android, or HarmonyOS.
• Integration guidance: retrieve initialization, framework adaptation, and call examples from the corresponding interface index; by default it shows code rather than writing project files.
• Event tracking: map action_type, required/optional events, and industry-specific parameters.
• Reconciliation: cover conversion testing, log queries, quality dashboards, and data checks.
• Troubleshooting and audit: use error codes, FAQs, integration debugging, and audit checks to find missing events, duplicate registration, redundant auto-collected events, and compliance issues.

Caveats

The automated integration assistant starts only when the user explicitly asks for integration, and stays within the initial Beta framework whitelist. It falls back to show-only guidance for monorepos, failed framework detection, or failed patch generation. The integration audit is intended for already-integrated projects, focusing on required-event coverage and initialization hygiene, not on single-event lookup or error-code debugging.