This product is not supported for your selected Datadog site. ().
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

aws_profile_domain

account_id

Type: STRING

created_at

Type: TIMESTAMP
Provider name: CreatedAt
Description: The timestamp of when the domain was created.

dead_letter_queue_url

Type: STRING
Provider name: DeadLetterQueueUrl
Description: The URL of the SQS dead letter queue, which is used for reporting errors associated with ingesting data from third party applications.

default_encryption_key

Type: STRING
Provider name: DefaultEncryptionKey
Description: The default encryption key, which is an AWS managed key, is used when no specific type of encryption key is specified. It is used to encrypt all data before it is placed in permanent or semi-permanent storage.

default_expiration_days

Type: INT32
Provider name: DefaultExpirationDays
Description: The default number of days until the data within the domain expires.

domain_name

Type: STRING
Provider name: DomainName
Description: The unique name of the domain.

last_updated_at

Type: TIMESTAMP
Provider name: LastUpdatedAt
Description: The timestamp of when the domain was most recently edited.

matching

Type: STRUCT
Provider name: Matching
Description: The process of matching duplicate profiles. If Matching = true, Amazon Connect Customer Profiles starts a weekly batch process called Identity Resolution Job. If you do not specify a date and time for Identity Resolution Job to run, by default it runs every Saturday at 12AM UTC to detect duplicate profiles in your domains. After the Identity Resolution Job completes, use the GetMatches API to return and review the results. Or, if you have configured ExportingConfig in the MatchingRequest, you can download the results from S3.

  • auto_merging
    Type: STRUCT
    Provider name: AutoMerging
    Description: Configuration information about the auto-merging process.

    • conflict_resolution
      Type: STRUCT
      Provider name: ConflictResolution
      Description: How the auto-merging process should resolve conflicts between different profiles. For example, if Profile A and Profile B have the same FirstName and LastName (and that is the matching criteria), which EmailAddress should be used?

      • conflict_resolving_model
        Type: STRING
        Provider name: ConflictResolvingModel
        Description: How the auto-merging process should resolve conflicts between different profiles.
        • RECENCY: Uses the data that was most recently updated.
        • SOURCE: Uses the data from a specific source. For example, if a company has been aquired or two departments have merged, data from the specified source is used. If two duplicate profiles are from the same source, then RECENCY is used again.
      • source_name
        Type: STRING
        Provider name: SourceName
        Description: The ObjectType name that is used to resolve profile merging conflicts when choosing SOURCE as the ConflictResolvingModel.

    • consolidation
      Type: STRUCT
      Provider name: Consolidation
      Description: A list of matching attributes that represent matching criteria. If two profiles meet at least one of the requirements in the matching attributes list, they will be merged.

    • enabled
      Type: BOOLEAN
      Provider name: Enabled
      Description: The flag that enables the auto-merging of duplicate profiles.

    • min_allowed_confidence_score_for_merging
      Type: DOUBLE
      Provider name: MinAllowedConfidenceScoreForMerging
      Description: A number between 0 and 1 that represents the minimum confidence score required for profiles within a matching group to be merged during the auto-merge process. A higher score means higher similarity required to merge profiles.

  • enabled
    Type: BOOLEAN
    Provider name: Enabled
    Description: The flag that enables the matching process of duplicate profiles.
  • exporting_config
    Type: STRUCT
    Provider name: ExportingConfig
    Description: Configuration information for exporting Identity Resolution results, for example, to an S3 bucket.
    • s3_exporting
      Type: STRUCT
      Provider name: S3Exporting
      Description: The S3 location where Identity Resolution Jobs write result files.
      • s3_bucket_name
        Type: STRING
        Provider name: S3BucketName
        Description: The name of the S3 bucket where Identity Resolution Jobs write result files.
      • s3_key_name
        Type: STRING
        Provider name: S3KeyName
        Description: The S3 key name of the location where Identity Resolution Jobs write result files.
  • job_schedule
    Type: STRUCT
    Provider name: JobSchedule
    Description: The day and time when do you want to start the Identity Resolution Job every week.
    • day_of_the_week
      Type: STRING
      Provider name: DayOfTheWeek
      Description: The day when the Identity Resolution Job should run every week.
    • time
      Type: STRING
      Provider name: Time
      Description: The time when the Identity Resolution Job should run every week.

rule_based_matching

Type: STRUCT
Provider name: RuleBasedMatching
Description: The process of matching duplicate profiles using the Rule-Based matching. If RuleBasedMatching = true, Amazon Connect Customer Profiles will start to match and merge your profiles according to your configuration in the RuleBasedMatchingRequest. You can use the ListRuleBasedMatches and GetSimilarProfiles API to return and review the results. Also, if you have configured ExportingConfig in the RuleBasedMatchingRequest, you can download the results from S3.

  • attribute_types_selector
    Type: STRUCT
    Provider name: AttributeTypesSelector
    Description: Configures information about the AttributeTypesSelector where the rule-based identity resolution uses to match profiles.
    • address
      Type: UNORDERED_LIST_STRING
      Provider name: Address
      Description: The Address type. You can choose from Address, BusinessAddress, MaillingAddress, and ShippingAddress. You only can use the Address type in the MatchingRule. For example, if you want to match profile based on BusinessAddress.City or MaillingAddress.City, you need to choose the BusinessAddress and the MaillingAddress to represent the Address type and specify the Address.City on the matching rule.
    • attribute_matching_model
      Type: STRING
      Provider name: AttributeMatchingModel
      Description: Configures the AttributeMatchingModel, you can either choose ONE_TO_ONE or MANY_TO_MANY.
    • email_address
      Type: UNORDERED_LIST_STRING
      Provider name: EmailAddress
      Description: The Email type. You can choose from EmailAddress, BusinessEmailAddress and PersonalEmailAddress. You only can use the EmailAddress type in the MatchingRule. For example, if you want to match profile based on PersonalEmailAddress or BusinessEmailAddress, you need to choose the PersonalEmailAddress and the BusinessEmailAddress to represent the EmailAddress type and only specify the EmailAddress on the matching rule.
    • phone_number
      Type: UNORDERED_LIST_STRING
      Provider name: PhoneNumber
      Description: The PhoneNumber type. You can choose from PhoneNumber, HomePhoneNumber, and MobilePhoneNumber. You only can use the PhoneNumber type in the MatchingRule. For example, if you want to match a profile based on Phone or HomePhone, you need to choose the Phone and the HomePhone to represent the PhoneNumber type and only specify the PhoneNumber on the matching rule.
  • conflict_resolution
    Type: STRUCT
    Provider name: ConflictResolution
    • conflict_resolving_model
      Type: STRING
      Provider name: ConflictResolvingModel
      Description: How the auto-merging process should resolve conflicts between different profiles.
      • RECENCY: Uses the data that was most recently updated.
      • SOURCE: Uses the data from a specific source. For example, if a company has been aquired or two departments have merged, data from the specified source is used. If two duplicate profiles are from the same source, then RECENCY is used again.
    • source_name
      Type: STRING
      Provider name: SourceName
      Description: The ObjectType name that is used to resolve profile merging conflicts when choosing SOURCE as the ConflictResolvingModel.
  • enabled
    Type: BOOLEAN
    Provider name: Enabled
    Description: The flag that enables the rule-based matching process of duplicate profiles.
  • exporting_config
    Type: STRUCT
    Provider name: ExportingConfig
    • s3_exporting
      Type: STRUCT
      Provider name: S3Exporting
      Description: The S3 location where Identity Resolution Jobs write result files.
      • s3_bucket_name
        Type: STRING
        Provider name: S3BucketName
        Description: The name of the S3 bucket where Identity Resolution Jobs write result files.
      • s3_key_name
        Type: STRING
        Provider name: S3KeyName
        Description: The S3 key name of the location where Identity Resolution Jobs write result files.
  • matching_rules
    Type: UNORDERED_LIST_STRUCT
    Provider name: MatchingRules
    Description: Configures how the rule-based matching process should match profiles. You can have up to 15 MatchingRule in the MatchingRules.
    • rule
      Type: UNORDERED_LIST_STRING
      Provider name: Rule
      Description: A single rule level of the MatchRules. Configures how the rule-based matching process should match profiles.
  • max_allowed_rule_level_for_matching
    Type: INT32
    Provider name: MaxAllowedRuleLevelForMatching
    Description: Indicates the maximum allowed rule level.
  • max_allowed_rule_level_for_merging
    Type: INT32
    Provider name: MaxAllowedRuleLevelForMerging
    Description: MatchingRule
  • status
    Type: STRING
    Provider name: Status
    Description: PENDING
    • The first status after configuration a rule-based matching rule. If it is an existing domain, the rule-based Identity Resolution waits one hour before creating the matching rule. If it is a new domain, the system will skip the PENDING stage.
    IN_PROGRESS
    • The system is creating the rule-based matching rule. Under this status, the system is evaluating the existing data and you can no longer change the Rule-based matching configuration.
    ACTIVE
    • The rule is ready to use. You can change the rule a day after the status is in ACTIVE.

stats

Type: STRUCT
Provider name: Stats
Description: Usage-specific statistics about the domain.

  • metering_profile_count
    Type: INT64
    Provider name: MeteringProfileCount
    Description: The number of profiles that you are currently paying for in the domain. If you have more than 100 objects associated with a single profile, that profile counts as two profiles. If you have more than 200 objects, that profile counts as three, and so on.
  • object_count
    Type: INT64
    Provider name: ObjectCount
    Description: The total number of objects in domain.
  • profile_count
    Type: INT64
    Provider name: ProfileCount
    Description: The total number of profiles currently in the domain.
  • total_size
    Type: INT64
    Provider name: TotalSize
    Description: The total size, in bytes, of all objects in the domain.

tags

Type: UNORDERED_LIST_STRING