DRamirez
Practitioner III
Joined 2 years ago
User Profile
User Widgets
Contributions
How to convert e-06 number to 0.0000... number with liquid
Hi everybody! I was wondering: I am getting a number with connected content that has 8 numbers behind the 0 (0.00000677). I want this number to show up with all of the numbers behind the 0, but for some reason Braze returns this:6,77e-06. Is there a way to keep the number like the 0.000... ? In the code I am using, I have some rules set up for how different number sizes should show, so maybe it could also be that i have done something wrong: <td align="right" style="font-size: 22px; font-family: Viga, Arial, Helvetica, sans-serif; color: #000000; font-weight: bold;"><span style="font-size:20px;">€ {% if coin_price == 0 %}{{coin_price | round: 2 | replace: ".", ","}}{% elsif coin_price < 0.0001 and coin_price > -0.0001 %}{{coin_price | round: 8 | replace: ".", ","}}{% elsif coin_price < 0.01 and coin_price > -0.01 %}{{coin_price | round: 6 | replace: ".", ","}}{% elsif coin_price < 1 and coin_price > -1 %}{{coin_price | round: 4 | replace: ".", ","}}{% else %}{{coin_price | round: 2 | replace: ".", ","}}{% endif %}</span></td> </tr>340Views0likes2Comments- 490Views0likes0Comments
Content blocks, made in Drag & Drop editor, have a smaller width then the email templates
Hi everybody! I was wondering, do other people also encounter the issue that the content blocks, made with the drag & drop editor, that they put in an email and have the same width as the email (600px), are being rendered smaller compared to the mail. I have checked the padding within the content block and the padding within the email itself but everything is set to 0, so I'm at a bit of a loss what to do. It creates issues for the content block that we use as a header as it doesn't line up with the usual content within the mail.408Views0likes2CommentsRe: Nested custom attributes in Custom HTML messages
Hi Max! Thanks for the answer! This is what I have been using and it seems to work perfectly for iOS, but for some reason, it will not work with Android. I contacted Braze eventually and the conclusion was that it was something that had to be requested in the product roadmap unfortunately 😅193Views0likes0CommentsRe: Nested custom attributes in Custom HTML messages
Hi Allan, Unfortunately not. In the end, Braze concluded that it was something that had to be requested through the product roadmap. For now, we just did the survey for iOS users only, and hopefully we will be able to send it out for Android users soon!498Views1like0CommentsRe: Embedded NPS Survey Via Email
Hi Allan! We have an email NPS survey that works exactly like that! So there is a campaign where we have a range of buttons from 0 to 10. We then have an action based canvas based on link alias clicks. In that canvas we let people go through several audience paths (with the filter “clicked specific alias in this campaign”), since braze can only do up to 8 paths during each audience step. So we start with 3 options (promotors, detractors & passives), and then they go through 10 different audience paths for each score type. Each one of them ends with a user update step (it used to be a webhook before the user update feature) where they get a custom attribute linked to their profile. Pros? You will see all the results in one canvas you can make quick calculations for each month by just filtering the date in the canvas Cons? It is quite a hassle to set up. As the email has a mobile and desktop view, this means it also has different buttons (2 aliases for each score type) that you have to track each time, so that is a lot of work in the delivery step and all the audience paths It only looks at the first time somebody clicks in that specific mail, so it could be that somebody made another choice, that will not get registered anymore.464Views2likes1CommentRe: setCustomUserAttribute is not setting nested object
HiDanPickaxe! Was this perhaps tested on an Android device? I also had a problem that a nested custom attribute wouldn't update with an HTML IAM when shown on an Android device. On iOS, everything seemed to work fine. When contacting support, they eventually came to the conclusion that it was something that had to be requested through the product roadmap. It could ofcourse be that this issue is not the same as mine, but maybe this helps!511Views1like1Comment