PRODUCT
Follow

Related Entities

Endpoints Using the rootContainer Object

Parent Objects

rootContainer Object Definition

Note

Note: The Required column includes the following values:

  • Required: The field must be included in the POST call.

  • Read-only: The field is received in the GET call and required in the PUT call. It is not required in the POST call. You cannot edit this field.

  • Optional: If the field was received in the GET call, include it in the PUT call. This field is editable.

  • Internal: (For Sizmek internal use) If the field was received in the GET call, include it in the PUT call.

Name

Description

Type

Required

Notes

type

String

Read-only

RootContainer

id

ID of the delivery group.

Integer

Read-only

relationsBag

Holds hierarchy entities (parent/children).

relationsBag Object

Read-only

version

Internal.

Integer

Read-only

childRotationType

Rotation type of subcontainers.

Integer

Required

subContainers

List of all base ad containers attached to this delivery group.

subContainers Object

Optional

childOptimizationMetric

Metric towards which the automatic optimization engine optimizes when the selected rotation method for a delivery group is automatic optimization.

String

Required

childConversionTagId

ID of the conversion tag towards which to optimize when the selected optimization metric is conversions.

Integer

Required

childConversionTagName

Name of the tag towards which the automatic optimization engine is optimizing.

String

Optional

Object JSON Example

subContainers Object

subContainers Object Definition

Note

Note: The Required column includes the following values:

  • Required: The field must be included in the POST call.

  • Read-only: The field is received in the GET call and required in the PUT call. It is not required in the POST call. You cannot edit this field.

  • Optional: If the field was received in the GET call, include it in the PUT call. This field is editable.

  • Internal: (For Sizmek internal use) If the field was received in the GET call, include it in the PUT call.

Name

Description

Type

Required

Notes

type

Type of object.

String

Read-only

subContainers

id

ID of the delivery group.

Integer

Read-only

rotationSetting

Rotation type.

rotationSetting Object

Required

masterAdId

Master ad ID for the delivery group ad.

Long

Required

name

Name of the ad.

String

Read-only

adName

Deprecated.

Deprecated

Deprecated

Object JSON Example

rotationSetting Object

rotationSetting Object Definition

Note

Note: The Required column includes the following values:

  • Required: The field must be included in the POST call.

  • Read-only: The field is received in the GET call and required in the PUT call. It is not required in the POST call. You cannot edit this field.

  • Optional: If the field was received in the GET call, include it in the PUT call. This field is editable.

  • Internal: (For Sizmek internal use) If the field was received in the GET call, include it in the PUT call.

Name

Description

Type

Required

Notes

type

Type of object.

String

Read-only

rotationSetting

enabled

Status of the ad.

Boolean

Required

rotationType

Type of rotation.

String

Required

datesAccordingToPlacements

Determines if a date range is specified for the placement.

Boolean

Required

Inherited from placement = true

startDate

Serving start date for the delivery group.

String

Required

Applicable only for time-based rotation.

endDate

Serving end date for the delivery group.

String

Required

Applicable only for time-based rotation.

dateRanges

Internal.

Internal

Internal

serveOnSpecificDaysAndHours

Settings for a range of hours.

Boolean

Required

Select true if you are using hours-based.

hoursPerDay

Cron expression that defines the days, in hours, in which the delivery group will be served.

hoursPerDay Object

Required

Object JSON Example

hoursPerDay Object

hoursPerDay Object Definition

Note

Note: The Required column includes the following values:

  • Required: The field must be included in the POST call.

  • Read-only: The field is received in the GET call and required in the PUT call. It is not required in the POST call. You cannot edit this field.

  • Optional: If the field was received in the GET call, include it in the PUT call. This field is editable.

  • Internal: (For Sizmek internal use) If the field was received in the GET call, include it in the PUT call.

NAME

DESCRIPTION

TYPE

REQUIRED

NOTES

hoursPerDay

Defines the days, in hours, in which the delivery group will be served.

Cron expression

Required

Object JSON Example

About Cron Expressions

Cron is a time-based job scheduler; the cron expression defines the entire setup in one single expression. In Sizmek Ad Suite, we use cron jobs in time-based serving to determine which hours and days of the week to serve creatives.

Building Cron Expressions

Cron Expression Structure

The cron expression has a defined structure. You define the different time parameters, and each parameter is separated by a space.

The structure is as follows:

<second> <minute> <hour> <day-of-month> <month> <day-of-week> <year>

Special Characters in Cron Expressions

Special characters in cron expressions include the following:

  • * (all): Specifies all of the values for a specific set. For example, setting * in the hours field means an ad serves each hour during a 24 hour period.

  • ? (any): Specifies any value for a specific set, and applies only to <Day-of-month> and <Day-of-week>.

  • - (range): Specifies a range of values. For example, setting 2 - 4 in the hour field, means the creative serves at 02:00 a.m., 03:00 a.m., and 04:00 a.m.

Note

Note: Set each day with a separate cron expression. For example, if you want to serve an ad on Friday and Saturday, between 02:00 a.m. - 03:00 a.m., add two cron expressions (comma separated) to the HoursPerDay object.

"hoursPerDay": ["* * 2-3 ? * 6", "* * 2-3 ? * 7"]

Object Fields and Values

The following table describes the object fields and values for cron expressions.

Note

Note: Currently, Sizmek Ad Suite only supports six-character cron expressions.

Name

Required

Values

Notes

second

Yes

*

Not supported

minute

Yes

*

Not supported

hour

Yes

Any number between 0 and 23. For a range, use “-“.

Example

  • 0 = midnight – 01:00 a.m.

  • 1 = 01:00 a.m. – 02:00 a.m.

day-of-month

Yes

?

Not supported

month

Yes

*

Not supported. To specify a month, set a start date and end date under Rotation Setting object.

day-of-week

Yes

Any number between 1 and 7.

  • Sunday = 1

  • Monday = 2

  • Tuesday = 3

  • Wednesday = 4

  • Thursday = 5

  • Friday = 6

  • Saturday = 7

year

Yes

*

Not supported. Serves according to the specified start date and end date under Rotation Setting object.

Cron Expression Examples

  • Serving for weekdays (Monday – Friday), each hour during a 24 hour period

    "hoursPerDay":
    ["* * 0-23 ? * 2", "* * 0-23 ? * 3", "* * 0-23 ? * 4", "* * 0-23 ? * 5", "* * 0-23 ? * 6"]
  • Serving for weekends (Friday - Saturday), from 08:00 a.m. to 08:00 p.m.

    hoursPerDay: ["* * 8-19 ? * 7", "* * 8-19 ? * 1"]
  • Serving for only one hour, Sunday 08:00 a.m. - 09:00 a.m.

     "hoursPerDay": ["* * 8 ? * 1"]
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk