Repository navigation
feat(targeting-client): recipient created_at (ER-5515) - #605
Open
utkuufuk-epilot wants to merge 1 commit into
Open
utkuufuk-epilot wants to merge 1 commit into
utkuufuk-epilot wants to merge 1 commit into
Conversation
Regenerated from the deployed Targeting API spec plus the recipient's created_at from targeting-api!105, which isn't deployed yet: when the entity became a recipient, shown as the "Added" column in the campaign recipients table. Also syncs the already deployed CampaignType, setupCampaign target_ids and changeCampaignStatus docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context: ER-5515, campaigns that add new matches of their target as recipients once a day.
Regenerates
@epilot/targeting-clienttypes:created_aton a campaign recipient: when the entity became a recipient (at launch, when it first saw the campaign in a portal or as a Next Best Action, or when the daily recipient check added it). The 360 campaign recipients table shows it as the "Added" column.CampaignTypewithproduct_recommendationsandtypeon the campaign;setupCampaignrequires exactly onecampaign.target_idsentry;changeCampaignStatusdocumentsCAMPAIGN_HAS_NO_PRODUCT_RECOMMENDATIONS.The spec is the deployed one (
npm run openapi) plus only thecreated_atfield from the Targeting API change that adds it, which isn't deployed yet. Merge and release after that change is on production.Changeset: minor bump of
@epilot/targeting-client.