Product

17/03/23

• ‘Connect’ sidebar item

  • This should show even if credential manager hasn’t been configured

  • If users navigate to ‘connect’ in sidebar without credential setup, the listing will be empty

• Campaign processr < visibility for publishers

  • For v1 this should be asingle toggle to apply to all publishers

  • V2 may have ‘per publisher selection’ if required

• Tab terminology

  • Changed from ‘Active Configurations’ and ‘Inactive Configurations' to ‘Pending Configurations’ and ‘Complete Configurations'

• Campaign selection (setup step)

  • Select ‘existing campaign’ should have advertiser filter first

  • Configration applying should be a 1 to 1 relationship, therefore the interface needs to change because you should only be able to select 1 campaign to apply the configuration to so no need for the ‘associated campaigns’ column on the listing. Users can then duplicate the campaign if they want to separate their lead delivery into multiple campaigns.

• Dashboard

  • New column to show if campaign is ‘connected’

• ‘Connect’ listing

  • Needs ‘domain’ column and ‘advertiser’ column

  • This means that users can add credentials for multiple enterprises and have campaigns from multiple sources come in (intentsify do this)

• ‘Job details’ for validation lists

  • Too many values to show if included on ‘jobs’ table, so dedicated table in ‘job details’ with pagniation will show values

• Step order changes

  • Mapping should be 2nd step as this dictates the mapping for jobs in step 3 because the form chosen from the linked enterprise would have all the mapping already setup, so this can be imported and then mapping is done without the need for any manual user inpuitinput

• Audit of changes

  • Details will be on system level

• Campaign level connect integration

  • The ‘connect’ integration will be added, but without bits like API key and domain and this is done via credential manager

• Configuration pending updates

  • On jobs step, have column for ‘type of update’ then highlight the jobs that are new, updated, removed

• Potentially merge management screen with ‘dashboard’ somehow, maybe new tab?

  • Instead, have indicator column on dashboard that campaign is ‘connected’to show campaigns that have ‘connect’ integration on

• Multiple ‘connect’ campaigns scenario

  • If a campaign with a configuration applied is duplicated, will it also be ‘linked’ to the recieving leads enterprise and receive leads?

• Changing the campaign to apply the configuration to

  • In the ‘configure’ dialog, the chosen campaign can be changed?

  • Or once it’s applied, then it cannot be changed and the link between the campaign and the configuration is permenant?

    • If this is the case, what happens if a customer accidentally chooses the wrong campaign to apply it to? Because the campaign link is permanent, they can’t change the campaign?

• Handing of updates

  • If a configuration change is made on recieving leads enterprise (i.e. a job is updated, job is added, job is removed) how do we track and send this across enterprises? Via job id?

• In mappings, currently can only reference fields in processr once a lead is in because the fields come from the lead data

  • Can we change behaviour so fields come from associated form on the campaign? Therefore a lead does not have to be submitted before fields can be referenced in any mappings.

  • Option to select ‘Unmapped’ if mapping is to be done later in the scenario where a different ‘mapping’ form is chosen and the field required for mapping is not available, so the field needs to be added after configuration is applied, therefore the ‘unmapped’ field allows the configure process to be completed and the field can be mapped later

• Configuration pending updates

  • On jobs step, have column for ‘type of update’ then highlight the jobs that have been added, changed, removed (tracked based on campaign ID)

• Audit of changes

  • Details will be on system level

• Campaign level connect integration

  The ‘connect’ integration will be added, but without bits like API key and domain and this is done via credential manager

  Audit

  • How detailed will the ‘notes’ be here? E.g. this connect configuration was applied to this campaign. Or this connect configuration with these jobs with these settings was applied to this campaign?