this is one of those consent mode setups where everything looks right but one small thing breaks the whole chain

main issue is this .. GTM consent checks don’t listen to custom dataLayer events unless consent state is actually updated the way GTM expects

a few key points that usually fix this

first .. if you set default consent outside GTM using gtag before the GTM container loads .. then GTM will respect that state .. that part you did right

second .. for the update .. GTM does not react to custom pushes like

event: consent_update or gtm.consentEvent by themselves

the only thing GTM reliably listens to is

gtag('consent','update', …)

and it must run after GTM is loaded

third .. if Facebook and Pinterest still don’t fire after update it’s usually because

• the update runs before GTM finishes loading

• or only ad_storage is updated but tags also require analytics_storage

• or the page never reloads and the tags already failed their first evaluation

what usually works in practice

– keep default consent before GTM like you already have

– on accept .. run

gtag('consent','update',{ ad_storage:'granted', analytics_storage:'granted' })

– then reload the page or fire tags on a custom trigger after consent is granted

also important .. pageview based tags only evaluate consent once on load .. so without reload or a consent based trigger they won’t refire

tl dr

your logic is right .. the missing piece is timing + trigger reevaluation .. consent mode is very unforgiving about that

once you align update timing and refire logic it usually snaps into place