SDK API Reference / CASPushResult
Interface: CASPushResult
Result of the CAS push operation
Properties
audienceDrift?
optionalaudienceDrift?:AudienceDrift
Attributes/behaviors on the server but absent from the local YAML, detected while updating an existing audience. Present whenever such drift exists — in dry-run this is always just detection (no write happened); in a real push it means deleteDrift was passed and the removal was actually applied (otherwise pushAudience bails before any write — see computeAudienceDrift's doc comment).
audienceId?
optionalaudienceId?:string
audienceName?
optionalaudienceName?:string
created
created:
object
activations
activations:
number
audiences
audiences:
number
folders
folders:
number
segments
segments:
number
renamedAttributeIds?
optionalrenamedAttributeIds?:RenamedEntityId[]
Real-push only (not dry-run — the old/new id comparison needs an actual write to compare against). Present whenever a rename was detected: the attribute/behavior always gets a new server-side id (CAS-719 — the backend destroys and rebuilds on any update, never reads an incoming id), so this surfaces the old→new id mapping for the caller to report, since anything else keyed on the old id needs to know it moved.
renamedBehaviorIds?
optionalrenamedBehaviorIds?:RenamedEntityId[]
updated
updated:
object
activations
activations:
number
audiences
audiences:
number
folders
folders:
number
segments
segments:
number