Request
The customer operations lead wants the latest profile values staged for review. The change feed has repeated keys, a timestamp tie and a new signup absent from the sales table.
Done
SANDBOX.CUSTOMER_RELEASE holds one row per customer after a deterministic MERGE. SANDBOX.CUSTOMER_RELEASE_SUMMARY is a secure view with REGION, CUSTOMERS and KNOWN_EMAILS. The sales source remains untouched. A new customer can have a NULL region because the feed doesn't supply one.
A customer release needs a reproducible source rule and a place to inspect its effect. Clone the sales customers into a sandbox table, choose the latest update per key, and merge into the clone. Keep the source table unchanged so you can compare the release with its baseline.
The feed doesn't contain every customer field. Its new signup therefore has no region unless another system supplies one; don't invent a region to make the report look complete. After applying updates, inspect email coverage by region and the newly inserted rows. Publish the final summary as a secure view. That protects its definition while grants still decide who may query it.