Integration & Setup

Agency : Publisher Expectations

Agency / Publisher Expectations and Integration Prerequisites

(Test Environment and Support Requirements)This document outlines the expectations from agencies and publishers to ensure smooth integration, testing, and deployment of HockeyCurve solutions across web and app environments.

🔹 1. Test / Staging Environment Availability

Agencies and publishers are expected to provide access to a test or staging environment prior to production deployment. This environment should closely mirror the production setup.

• Desktop / MWeb:Test or preview URLs where sample ad tags can be loaded (e.g. staging or sandbox pages).
• App:A staging app build with HockeyCurve integration enabled.

🔹 2. Test Credentials & Access

The following may be required for validation:

• Test app builds (APK / IPA) or test URLs
• Test credentials, access tokens, or user IDs
• Feature flags or configurations needed to enable integration

App-specific example:For app integrations (e.g., Paytm), a test user ID should be shared. If a mobile number is required, use9711415617.

All shared access must be non-production and time-bound.

🔹 3. Integration Readiness

• Allow third-party sample ad tag rendering where applicable
• No blocking of required network calls via CSP, WebView rules, or firewalls unless documented
• Support click and impression tracking as per agreed integration flow

🔹 4. Test Cases Covered During Validation

Web / Desktop / MWeb

• Ad renders correctly on test or preview URL
• Interactive functionality works as expected
• Click tracking fires correctly
• Impression tracking fires on successful render
• Ad code reviewed to ensure no unauthorized scripts

App

• Ad renders correctly in staging app
• Interactive behavior functions as expected
• Click and impression tracking events fire correctly
• No conflicts with WebView or SDK policies

🔹 5. Logging & Debug Support

In case of issues, agencies or publishers should share:

• Network logs (failed or blocked requests)
• Console logs or error messages
• Screenshots or screen recordings (if applicable)

🔹 6. Validation & Sign-off

• All functionality validated in test or staging
• Deviations documented and reviewed
• Formal confirmation provided before production

🔹 7. Change Management

Any changes that may impact integration (SDK updates, policy changes, app upgrades, WebView changes) must be communicated in advance.

🔹 8. Responsibility Clarification

Issues not reproducible in provided test or staging environments may require additional inputs from the agency or publisher side. Timely collaboration is expected to ensure stability.

Back to all guides