Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Platform URL

https://[enterprise].cvtr.io/v2/…./campaigns/{campaignId}/admin/scheduled-delivery

API Endpoints

GET /api/v4/

…..

Epic

Not Applicable

Epic

Jira Legacy
serverSystem Jira
serverId47839f05-61cf-355f-8da7-a069f30ee70e
keyCON-5548

Document status

Status
colourBlue
titleDRAFTREADY FOR REVIEW

Document owner

Danny Hannah Adam Carter

Technical writers

Arunima Kurup Prasad

Related Content

Scheduled Delivery

🏠 Feature Overview

Using Scheduled Delivery, leads are scheduled to be delivered at different times and at different intervals. The schedule is configured using the ‘configuration’ widget available in the ‘Schedule’ column on the Scheduled Delivery page. This widget is the basis for both Campaign based Scheduled Delivery and Publisher based Scheduled Delivery and allows us to configure the schedule at various intervals as explained below.

...

By default, there are 4 mandatory fields to be filled in by the user.

  1. Start Date: This is a calendar field that can be used to configure the date on which Scheduled Delivery must begin on the campaign.

...

There is validation on the platform to ensure that the Start Date lies between the campaign’s start and end dates.

...

  1. Repeat Every

This setting determines the schedule interval. By default, the value is set to ‘1' and repeat unit is set as ‘Week(s)’. This means, the configured schedule will repeat every 1 week from the 'Start Date’ configured.

...

If the repeat unit selected is Week(s) or Month(s), then the ‘Repeat On’ configuration will be available. If the repeat unit selected is Day(s), then the ‘Repeat On’ configuration will not be available.

  1. Repeat On

The ‘Repeat On’ option will be available only if repeat unit selected is Week(s) or Month(s).

...

The days of the week can be configured as per the requirements of the campaign. The next scheduled date is calculated as below when the repeat unit is ‘Week(s)’:

Start date

Repeat interval (weeks)

Repeat on

Schedule previously run on:

Current date

Expected next scheduled date

2024-09-01 (Fri)

2

Fri, Wed

Not available

2024-09-01

2024-09-01 (Fri)

2024-09-01 (Fri)

2

Fri, Wed

Not available

2024-09-02

2024-09-13 (Wed)

2024-09-01 (Fri)

2

Fri, Wed

Not available

2024-09-07

2024-09-13 (Wed)

2024-09-01 (Fri)

2

Fri, Wed

Not available

2024-09-13

2024-09-13 (Wed)

2024-09-01 (Fri)

2

Fri, Wed

2022-09-13

2024-09-13

2024-09-15 (Fri)

2024-09-13 (Wed)

2

Fri, Wed

Not available

2024-09-13

2024-09-13 (Wed)

When repeat unit is ‘Month(s)’, user will be able to select the day of the month on which the schedule must repeat. The following options are available for monthly scheduled delivery:

...

The next schedule date is calculated as below when the repeat unit is ‘Month(s)’:

Start date

Repeat interval (months)

Repeat on

Previous scheduled date

Schedule previously run on:

Current date

Expected next scheduled date

2024-09-01

2

First day of month

Not available

2024-09-01

2024-09-01

2024-09-02

2

First day of month

Not available

2024-09-01

2024-11-01

2024-09-01

2

First day of month

Not available

2024-09-02

2024-11-01

2024-09-01

2

First day of month

Not available

2024-10-01

2024-12-01

2024-09-01

2

First day of month

Not available

2024-11-01

2024-11-01

2024-09-01

2

First day of month

2024-09-01

2024-09-01

2024-11-01

2024-09-01

2

First day of month

Not available

2024-09-15

2024-11-01

2024-08-28

1

nth day of the month (n=28)

Not available

2024-09-01

2024-09-28

2024-08-28

1

nth day of the month (n=28)

Not available

2024-09-30

2024-10-28

2024-01-29

1

nth day of the month (n=29)

Not available

2024-01-15

2024-01-29

2022

2025-01-29

1

nth day of the month (n=29)

2022

2025-01-29

2022

2025-02-01

2022

2025-03-29 (

2022

2025 not being a leap year, feb is skipped)

2024-01-29

1

nth day of the month (n=29)

2024-01-29

2024-02-01

2024-02-29 (2024 being a leap year)

2025-01-30

1

nth day of the month (n=30)

2025-01-30

2025-02-01

2022

2025-03-30 (feb is skipped)

2022

2025-01-31

1

nth day of the month (n=31)

2022

2025-01-31

2022

2025-02-01

2022

2025-03-31 (feb is skipped)

2022

2024-

07

09-15

1

15th (nth) day of the month

Not available

2022

2024-

07

09-15

2022

2024-

07

09-15

2022

2024-

07

09-15

1

15th (nth) day of the month

2022

2024-

07

09-15

2022

2024-

07

09-15

2022

2024-

08

10-15

2022

2024-

07

08-01

1

Last day of the month

Not available

2022

2024-

07

08-01

2022

2024-

07

08-31

2022

2024-07-01

1

Last day of the month

2022

2024-07-31

2022

2024-07-31

2022

2024-08-31

2022

2024-07-01

2

Last day of the month

Not available

2022

2024-07-01

2022

2024-07-31

2022

2024-07-01

2

Last day of the month

2022-07-31

2022

2024-09-30

2022

2024-09-30

2022

2025-01-01

1

Last day of the month

2022

2025-01-31

2022

2025-02-01

2022

2025-02-28

2024-02-01

1

Last day of the month

Not available

2024-02-01

2024-02-29 (2024 being a leap year)

2022

2025-02-01

1

Last day of the month

2022

2025-02-28

2022

2025-03-01

2022

2025-03-31

2022

2025-02-01

2

Last day of the month

2022

2025-02-28

2022

2025-02-28

2022

2025-04-30

2024-01-01

1

Last day of the month

2024-01-31

2024-02-01

2024-02-29 (2024 being a leap year)

2022-07-01 (Fri)

1

Last day of the month (excl. weekends)

Not available

2022-07-20

2022-07-29 (Fri) since 2022-07-31 is a Sunday

2022

2024-

07

03-01 (Fri)

1

First day of the month (excl. weekends)

Not available

2022

2024-

07

06-01 (Sat)

2022

2024-07-01 (

Fri

Mon)

2022

2024-

07

03-01 (Fri)

3

First day of the month (excl. weekends)

Not available

2022

2024-

07

06-01 (

Fri

Sat)

2022

2024-07-

152022-10-03

01 (Mon)

since 2022-10-01 is a Sat

  1. Hour

The 'Hour' is a dropdown listing values from 00 to 23 from which the user can select the hour at which the schedule must run.

\uD83D\uDDD2 Summary

Summarise the functionalities in a table

A user can add, remove and reset columns for custom table

Functionality

User Story

1

Start Date

Admin and Agency users can configure the date on which the schedule must start on a campaign, the date must lie within the campaign start and end dates

2
3

Table Filtering

Allows the user to filer the table values using column names

4

Custom Tables

Repeat Every

This configuration determines whether the schedule should be executed every day/month/week

3

Repeat On

  • When Repeat Every selected is ‘Week(s)’: the schedule can be configured to repeat on the days of the week

  • When Repeat Every selected is ‘Month(s)’: the schedule can be configured to repeat on various days of the week such as 1st day of the month (including/excluding weekends). last day of the month (including/excluding weekends). Nth day of the month where N is the date configured in ‘Start Date’

4

Hour

This is the hour at which schedule will be delivered

\uD83D\uDDD2 User Permissions

Mention if access needs to be enabled for any user roles and attach the user matrixOnly Admin and Agency users have access to Scheduled Delivery.

https://docs.google.com/spreadsheets/d/1i4qTTKkC3rF3EyEOh2585ktDDGge0L0IMVDNCwriFR0/edit#gid=415459484