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 input

• 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

• Form field mapping

  • 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 listing

  • Have 3 tabs instead of 2 tabs (previously ‘active’ and ‘inactive’)

    • ‘New configurations'

    • ‘Updated configurations' (this will need a column to show ‘linked campaigns’)

    • ‘Complete configurations' (this will need a column to show ‘linked campaigns’)

• Multiple ‘connect’ campaigns scenario

  • Intentsify use case have multiple campaigns sending to 1 linked enterprise campaign

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

      • It will not be possible to apply configurations to multiple campaigns, but the ‘connect’ integration will still persist if duplicated, and leads can still be sent from multiple campaigns on sending leads enterprise to the receiving enterprise

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

  • Instead, have column on dashboard to show campaigns that have ‘connect’ integration on

Product

22/03/23

• 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?

    • Rokas: yes job id, map on the backend so we know which job corresponds to which job between enterprises

• Configure dialog > mapping step

  • Mapping fields only required if they choose their own form. If they choose the form as the form chosen on the linked enterprise then mapping not required

• Configure dialog > jobs step

  • Validation list values change from table of values to ‘download’ values button (private validation list will not allow downloading of values)

• Job names

  • Include actual jobs for examples

• 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?

    • It will be granular

    • Campaign level audit as well

• Campaign > processr

  • Have an indicator that it’s from ‘connect’

• Changing the linked campaign

  • 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? Have a way to ‘unlink’ the campaign and then the configuration can be applied again.

• 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?

• It will not be possible to apply configurations to multiple campaigns, but the ‘connect’ integration will still persist if duplicated, and leads can still be sent from multiple campaigns on sending leads enterprise to the receiving enterprise

Import all jobs from another campaign

Import all jobs from another campaign

• Are we doing this for v1? If so, need to scope this?

  • Will it import and replace any existing jobs? Can you select which jobs to import?