Traffic and Infra

The ‘Traffic’ and ‘Infra’ module provides the means for managing traffic campaigns and suppplementary resources.

The below diagram shows the relationship between key resources in the ‘Traffic’ module.

erDiagram
    CAMPAIGN }o..o{ TRAFFIC_SOURCE : uses
    CAMPAIGN }o--|{ TEMPLATE : directs_to
    DOMAIN }o--|| SERVER : exists_on
    TEMPLATE }o..o{ DOMAIN : deployed_at
    AFFILIATE_NETWORK
    API_INTEGRATION ||--o{ SERVER : provides
    API_INTEGRATION ||--o{ DOMAIN: provides

A traffic campaign can optionally use a traffic source to configure custom URL parameters applied to the campaign link. A campaign must also use one or more templates (white pages, lander pages or pre-lander pages) as a destination where the audiences that click on the campaign link must be sent to. Templates are deployed at domains which exist at specific servers. Domains and servers are purchased via API integrations with external providers.

Affiliate networks are not involved in this flow. Instead, this resource type allows for integrating Eversend traffic campaigns with external means of managing affiliate activity. The same is true for API integrations: this resource represents links between Eversend and various infrastructure providers.

The basic flow of using the ‘Traffic’ and ‘Infra’ modules is as follows.

1. Add new API integrations with domain and server providers.

2. Use these integrations to add new domains and new servers.

3. Upload new templates of the required types.

4. Optionally, set up traffic sources for easy management of URL parameters.

5. Create and launch new traffic campaigns.